Skip to content
This repository has been archived by the owner on Oct 12, 2023. It is now read-only.

Applicationset and Application belong to the same namespace #589

Open
Hargeek opened this issue Jun 8, 2022 · 1 comment
Open

Applicationset and Application belong to the same namespace #589

Hargeek opened this issue Jun 8, 2022 · 1 comment

Comments

@Hargeek
Copy link

Hargeek commented Jun 8, 2022

I expect the application generated by applicationSet to use the same name, which requires it to be generated under a different namespace. Explain also has the namespace field

kubectl explain applicationset.spec.template.metadata.namespace
KIND:     ApplicationSet
VERSION:  argoproj.io/v1alpha1

FIELD:    namespace <string>

DESCRIPTION:
<empty>

In fact, it can only be generated to the same namespace as applicationSet
An error is as follows

time="2022-06-08T08:32:46Z" level=error msg="validation error found during application validation: ApplicationSet helloworld contains applications with duplicate name: helloworld"
time="2022-06-08T08:32:46Z" level=error msg="validation error found during application validation: ApplicationSet helloworld contains applications with duplicate name: helloworld"

Indeed, the examples in the reference documentation do not use namespace

@nmohoric
Copy link

Ran into this as well. It's surprising that the CRD does allow a namespace on the template but it doesn't appear to actually be used.
Sadly my golang isn't good enough to feel comfortable trying to fix this. Hopefully there's more interest out there to get this fixed.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants