You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using ApplicationSets to conditionally deploy resources to clusters.
For example, I would like to deploy a web application only on clusters that have the webApp.enabled property set to "true".
I'm using the matchLabel selector to set the condition, however it seems it doesn't support dots in key names.
To Reproduce
Here's a sample definition of a cluster (clusters/test.yaml):
I was able to work around by putting the key at the root at the document (webAppEnabled), however I would prefer to have it part of the webApp object. The following definition works:
Is the matchLabels selector even supported for git generators?
You'll notice that the cluster generator page in the documentation contains a Table of contents entry for Label selector. However, the git generator page does not.
The yaml is accepted by the admission controller when you define an ApplicationSet using a git generator with the matchLabels selector. However, in my experience, it just prevents the ApplicationSet from matching any clusters successfully. And no applications are created as a result.
That's what I thought too, until I found argoproj/applicationset#361 (fixed by #9312).
So it seems selectors are available for all kinds of generators, however here the point is about supporting label keys with dots in it (webApp.enabled instead of webAppEnabled).
I didn't test it, but I expect this behavior to be the same with other types of generators.
Describe the bug
I'm using ApplicationSets to conditionally deploy resources to clusters.
For example, I would like to deploy a web application only on clusters that have the webApp.enabled property set to "true".
I'm using the matchLabel selector to set the condition, however it seems it doesn't support dots in key names.
To Reproduce
Here's a sample definition of a cluster (
clusters/test.yaml
):And the corresponding ApplicationSet, which doesn't work -- no Application gets created:
I was able to work around by putting the key at the root at the document (
webAppEnabled
), however I would prefer to have it part of the webApp object. The following definition works:Am I missing something here, or is this not supported by the ApplicationSet controller?
Expected behavior
I would expect the ApplicationSet controller to accept dots in the name of the key, as it is possible in Kubernetes.
Version
The text was updated successfully, but these errors were encountered: