CODEWITHSUNDEEP
consul
Amit Kumar Jain
Amit Kumar Jain

Reputation: 487

Consul Intentions are not working for consul services

My consul set up is as follows: -

consul-01 server on 192.168.30.112
consul-02 server on 192.168.30.113
consul-03 server on 192.168.30.114
consul-client on 192.168.30.115
consul-client on 192.168..30.116

I have registered 3 .NET Core services viz. service1, service2 and service3. 2 instances of service1 and service2 running on 192.168.30.115 and 192.168.30.116. 1 instance of service3 is running on 192.168.30.116. My use case is that service1 is talking to service2 and service2 in turns talking with service3. All is working fine. Now when i defined an intention as consul intention create -deny service1 service2, I am supposed that it must give me an error when I hit the url of service1, but it gives proper output to me. I am not using any sidecar-proxy in my setup. I just want to know that whether intentions only work with side-car proxy or they work work without it also.

Thanks

Upvotes: 0

Views: 584

Answers (1)

Blake Covarrubias
Blake Covarrubias

Reputation: 2303

Consul intentions are authorization polices that allow you to control access between applications within a service mesh. You must use a sidecar proxy, or natively integrate your application with the mesh, in order to use intentions. They are not applicable if you are only using Consul for service discovery.

Upvotes: 1

Related Questions