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

Trigger by the source label #41

Open
1995parham opened this issue Aug 19, 2024 · 0 comments
Open

Trigger by the source label #41

1995parham opened this issue Aug 19, 2024 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@1995parham
Copy link
Member

Right now, the only trigger to change the appproj is adding appproj label, it means if you have namespace (consider parham-testing) which parham team wants to deploy their pods, etc. into it then you can label it as follows:

apiVersion: v1
kind: Namespace
metadata:
  labels:
    argocd.snappcloud.io/appproj: argocd
  name: parham-testing

and then you will have it as a destination:

apiVersion: argoproj.io/v1alpha1
kind: AppProject
metadata:
  name: argocd
  namespace: user-argocd
spec:
  destinations:
  - namespace: parham-testing
    server: https://kubernetes.default.svc

If they, after a while, decided to have it for their Argo CD applications too, then you need to label it as follows:

apiVersion: v1
kind: Namespace
metadata:
  labels:
    argocd.snappcloud.io/appproj: argocd
    argocd.snappcloud.io/source: argocd
  name: parham-testing

But the operator doesn't change the appproject which is wrong.

@1995parham 1995parham added the bug Something isn't working label Aug 19, 2024
@1995parham 1995parham self-assigned this Aug 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant