Initially it worked good but when I have applied intention to deny traffic from counting to dashboard it denied the traffic but when I delete the same intention from consul UI, the rule got deleted but still service was unreachable. This is odd I have also checked kubectl get ServiceIntentions and there are no rules.
Hi @magr90900, this sounds like Envoy might have been re-using an existing connection to the upstream which was still subject to the deny policy (see Intentions: Enforcement).
How long did this problem persist? Did the connection eventually start working after some time?