[DRAFT] Implement standalone-hub-templating #332
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When ConfigurationPolicy or OperatorPolicy is deployed directly to the managed cluster, for example via GitOps, it skips the step in the policy framework that would normally resolve hub templates. This feature allows the config-policy-controller to be configured with a kubeconfig in order to access the hub cluster and resolve those templates. When the new argument to enable this is not set, unresolved hub templates will result in a specific compliance message to report this situation. Limitations on what the hub templates can access are managed only through the permissions that the given hub kubeconfig has. To handle situations where the hub cluster can not be accessed (especially temporarily), the policy state after resolving hub templates will be cached on the managed cluster in a secret. Refs: - https://issues.redhat.com/browse/ACM-16091 - https://github.com/open-cluster-management-io/enhancements/tree/main/enhancements/sig-policy/134-standalone-hub-templates Signed-off-by: Justin Kulikauskas <[email protected]>
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: JustinKuli The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When ConfigurationPolicy or OperatorPolicy is deployed directly to the managed cluster, for example via GitOps, it skips the step in the policy framework that would normally resolve hub templates. This feature allows the config-policy-controller to be configured with a kubeconfig in order to access the hub cluster and resolve those templates. When the new argument to enable this is not set, unresolved hub templates will result in a specific compliance message to report this situation.
Limitations on what the hub templates can access are managed only through the permissions that the given hub kubeconfig has.
To handle situations where the hub cluster can not be accessed (especially temporarily), the policy state after resolving hub templates will be cached on the managed cluster in a secret.
Refs: