New OPA environment. #679
Replies: 1 comment
-
Closing because I ended up duplicating ... my bad! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hey guys,
First of all, I'm becoming a big fan of this tool, it's awesome! I'm from Cyber Security and I'm new to the OPA world.
We are currently deploying Gatekeeper in my organization, which is controlling my entire k8s environment, in conjunction with Terraform/Atlantis. Later this year, we want to migrate our entire environment to kubernetes!
In the above environment, we have policies in production and everything works fine! But I would like to know how to build a new approach for another environment, outside of kubernetes.
I have a cloud environment that is currently accessed by a limited number of people, but they can make significant changes within the dashboard. For example, letting a security group accept ingresses to 0.0.0.0./0.
My question, I already know that Gatekeeper only works within k8s, so would I have to have another OPA environment (other than Gatekeeper) installed to control these aspects via Terraform or something else I don't know yet (Lambda function?), via Rego policies?
For example: I want an OPA policy not to allow an SG to be created or changed (CREATE or UPDATE) when it violates the Rego rule that doesn't allow ingress to 0.0.0.0./0.
Is it possible to create a project to control a cloud environment like this?
Beta Was this translation helpful? Give feedback.
All reactions