Visibility of why http.send is not working #701
Unanswered
tg-44
asked this question in
OPA and Rego
Replies: 1 comment 1 reply
-
Hi there! On my phone but you’ll want to look into:
|
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I am struggling to understand why my Rego does not seem to behaving as expected when deployed along side my OPA service in Kubernetes.
The example Rego can be found here, note its a very contrived example but illustrates the problem I am having.
https://play.openpolicyagent.org/p/GoxD6aXwGN
I can get this to work fine when using OPA eval and with the URL pointing to a locally running API. So I know the Rego is fine.
But when deploying the OPA server to Kubernetes, and with the Rego URL pointing to an internal Kubernetes services it does not work.
The fact it doesn't work is fine, as if I can work out what the issue is then i can iterate to resolve the problem.
But the problem is I have NO visibility whatsoever of what's going on.
I have enabled debug logging on the server, then viewed the pod logs; but this does not seem to surface issues encountered in the Rego.
I have enabled decision logs, but this is also the same.
How on earth do you get the visibility necessary to be able to identify what is going wrong so that you can make changes to resolve the problem?
see below my Kubernetes deployment.
Any idea how I can debug what is happening by getting some visibility of what is failing?
Beta Was this translation helpful? Give feedback.
All reactions