-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pkg/helm: add option to watch dependent resources #885
pkg/helm: add option to watch dependent resources #885
Conversation
…ips between owner and child resources
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, just one question.
GVK: gvk, | ||
ManagerFactory: factory, | ||
ReconcilePeriod: helmOperatorFlags.ReconcilePeriod, | ||
WatchDependentResources: true, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should watching dependent resources be configurable, or is this always being true
fine for up local
purposes?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It probably makes sense to make this configurable in both the up local
and in-cluster scenarios.
Since this is also a feature of the ansible operator, how about we do a follow-up PR to add a flag for this to the pkg/internal/flags.WatchFlags
struct?
@shawn-hurley, any input from the ansible operator perspective (or otherwise)?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
We can try to make the option configurable in a follow up.
Description of the change:
Adding option to enable watches of dependent resources of Helm releases.
Motivation for the change:
Currently, the helm operator must perform a periodic reconciliation to ensure that dependent resources do not drift from their release manifest. This periodic reconciliation is often a no-op since no changes have occurred. This PR will reduce resource utilization in the operator and against the API server by eliminating the need for periodic reconciliation.