-
Notifications
You must be signed in to change notification settings - Fork 137
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
Onboarding a "light" cluster #419
Comments
This sounds reasonable to me -- did you want these resources managed by argocd as well? or just git tracked? |
Oh, ideally using argocd. |
Sounds good to me. If you want to manage it via argocd, I'd suggest to import it to our ACM which will take care of the ArgoCD setup |
@larsks let us know if this is something you'll be doing, otherwise we will need an SA sitting in this new cluster with cluster admin that argocd can use to login. |
We installed it using ACM (https://multicloud-console.apps.moc-infra.massopen.cloud/multicloud/clusters/curator/overview), but if there's any specific metadata we need to set that says "we're going to manage this using argocd", we didn't set that. |
Just update the spec:
applicationManager:
argocdCluster: true And you're all set 👍 |
That reminds me, until ACM BZ 1939096 is resolved, we should probable reserve the namespaces which are created by ACM for the managed clusters in this repo so we don't accidentally touch it... |
@larsks additionally to that you want to create a similar ArgoCD app for the curator: And create app of apps: @HumairAK I wonder, can we move the app of apps to the |
This adds configuration for the curator cluster [1]. Closes #419 [1]: https://console-openshift-console.apps.curator.massopen.cloud/dashboards
We've recently deployed an OCP 4.7 bare metal cluster for the Curator project. I'd like to manage some aspects of the cluster through this repository (e.g., the default ingress certificate, the connection with the SSO environment, etc), but there will be other cluster admins who will be "doing their own thing". The overlay configuration would be minimal, probably something like:
Does this seem like a reasonable plan?
The text was updated successfully, but these errors were encountered: