-
Notifications
You must be signed in to change notification settings - Fork 32
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
chore: Add support for argocd in install-gitops script #322
base: main
Are you sure you want to change the base?
Conversation
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.
Just two little notes, suggestions in comments
- Attempted to validate the default behaviour or quick start by running
make quick-start
but reconciliation of the namespace was unsuccessful as the flux resources were being created on the wrong cluster - Attempted to validate the use of the argo path by running
GITOPS_PROVIDER=argo ./scripts/install-gitops --context kind-worker --git
but observed that the env var was being reset to flux
Co-authored-by: Sapphire Mason-Brown <[email protected]>
@@ -238,15 +238,15 @@ setup_worker_destination() { | |||
${ROOT}/scripts/register-destination --name platform-cluster --context kind-platform $flags | |||
else | |||
cat "${ROOT}/config/samples/platform_v1alpha1_worker.yaml" | patch_statestore | kubectl --context kind-platform apply --filename - | |||
install_gitops kind-worker worker-1 | |||
install_flux_gitops kind-worker worker-1 |
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.
Not sure you want to block this PR, but should we have an Argo flag for the worker gitops too?
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.
eventually yes!
No description provided.