Skip to content
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

common automatic update #344

Merged

Conversation

mbaldessari
Copy link
Contributor

  • Small gitops channel cleanups
  • Upgrade namespaced argocd version to v1beta1
  • Stop using OpenShiftControllerManager lookups
  • Update tests after common rebase

mbaldessari and others added 8 commits February 20, 2024 17:46
Mainly for consistency reasons. gitops-1.11 is already the default
Upgrade namespaced argocd version to v1beta1
When applying the policy to install the cluster-wide argo on regional
clusters, we do some lookups() on the regional cluster in order to
pass the version values, domain names, etc.

To get the cluster version we were using the OpenShiftControllerManager
which is problematic because it does not exist on hyper-shift clusters.

Let's switch to use the ClusterVersion.status.history[0].version entry.

The only smaller caveat is that due to limitations in go templates +
sprig functions, we cannot really take the last version only when the
state is "Completed", but we simply take the last version.

This means that during a cluster upgrade on a regional cluster, we will
include values of the version the cluster is upgrading to, which is
less than ideal, but it should eventually converge in any case.

For reference the function that guarantees that the ordering of the
history status in ClusterVersion is preserved is here:
https://pkg.go.dev/github.com/openshift/api/config/v1#ClusterVersionStatus

Tested on Lester's cluster and on a local cluster of mine.

Co-Authored-By: Lester Claudio <[email protected]>
Stop using OpenShiftControllerManager lookups
@mbaldessari mbaldessari merged commit 8af9025 into validatedpatterns:main Feb 22, 2024
4 checks passed
tim-stasse pushed a commit to tim-stasse/multicloud-gitops that referenced this pull request Mar 18, 2024
…_files

Add extra value files and nulling logic to allow "disabling" applications
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant