Skip to content

fix: create separate namespaces app, if destination is remote#30

Merged
thesuperzapper merged 1 commit into
deployKF:mainfrom
thesuperzapper:namespaces-app-for-remote
Sep 21, 2023
Merged

fix: create separate namespaces app, if destination is remote#30
thesuperzapper merged 1 commit into
deployKF:mainfrom
thesuperzapper:namespaces-app-for-remote

Conversation

@thesuperzapper

Copy link
Copy Markdown
Member

This PR fixes an issue that prevented deployments from "management" ArgoCD clusters into remote "destination" clusters.

The issue was that the deploykf-app-of-app ArgoCD application contained the namespaces, which would mean that they were deployed onto the "management" cluster, rather than the "destination".

To ensure backward compatibility, the deploykf-namespaces app will only appear if the argocd.destination is NOT in-cluster or https://kubernetes.default.svc, otherwise they remain in the deploykf-app-of-app app.

@thesuperzapper thesuperzapper added this to the v0.1.2 milestone Sep 21, 2023
@thesuperzapper
thesuperzapper force-pushed the namespaces-app-for-remote branch from 4828aaa to ddc438a Compare September 21, 2023 19:02
@thesuperzapper
thesuperzapper merged commit 6d0698d into deployKF:main Sep 21, 2023
@thesuperzapper
thesuperzapper deleted the namespaces-app-for-remote branch September 21, 2023 19:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant