-
Notifications
You must be signed in to change notification settings - Fork 13
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
ROX-24494: ACSCS Addon overrides in Gitops lingers after removing from Gitops #2186
base: main
Are you sure you want to change the base?
Conversation
@@ -168,6 +165,39 @@ func (p *AddonProvisioner) provisionAddon(dataplaneClusterConfig gitops.DataPlan | |||
return | |||
} | |||
|
|||
func (p *AddonProvisioner) augmentGitopsWithOCMDefaultValues(expectedConfig *gitops.AddonConfig) error { | |||
if expectedConfig.Version == "" { |
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.
What is this condition about?
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.
You can specify the addon version in the gitops config. If you do not do this, the latest version will be installed.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kovayur, kurlov, ludydoo 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 |
Description
There is only a PATCH endpoint for updating addons in OCM.
So when a parameter is removed from the gitops config, it is not removed from the addon installation or switched to default value as expected, but remains there unmodified. As a result, there will always be a mismatch between the addon installed on the cluster and the expected state of the addon represented in the gitops config.
The proposed solution is to get all the default parameters for the given addon version and enrich the expected addon parameters by the default values.
This will only help if the engineer wants to switch from the value defined in gitops to the default value defined in OCM. When they need to remove a parameter from OCM, it always requires a new version to be released in OCM..
So the full procedure of removing the parameter, will look like the following:
Checklist (Definition of Done)
Test manual
ROX-12345: ...
Test manual
Unit tests