Graduate Config to beta
What steps did you take and what happened: [A clear and concise description of what the bug is.] Think about beta requirements for Config resource.
What did you expect to happen:
Anything else you would like to add: [Miscellaneous information that will assist in solving the issue.]
Environment:
- Gatekeeper version:
- Kubernetes version: (use
kubectl version):
since we recommend syncset, do we want to graduate to beta for sync? can/should we graduate for exclusions only?
+1, I agree. Let's think about how we can move config to beta in this case. Meanwhile I created an issue to track SyncSet beta graduation just for data replication - https://github.com/open-policy-agent/gatekeeper/issues/4116.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions.