Robert Jerzak

This issue is also related to more cases: - kustomize with remote base (e.g. the manifests of a git url tag) - custom plugin which fetches data from external sources...

@gebn assuming that clusters are defined in Argo CD with names (cluster1, cluster2) we could do something like this: ``` apiVersion: argoproj.io/v1alpha1 kind: ApplicationSet metadata: name: myapp spec: generators: -...

Another option would be to label existing cluster secrets with `name=' and then: ``` apiVersion: argoproj.io/v1alpha1 kind: ApplicationSet metadata: name: myapp spec: generators: - clusters: selector: matchLabels: name: cluster1 -...

Thanks @SergeyBear

Thanks @andyzasl It seems that there is missing last part of stack trace, could you please provide full version of error message generated?

@MO-BrandonR having one server for multiple functions is perfectly fine - if you have all those functiions defined in ansible there is no problem in creating proper version of variable...

Thanks @andyzasl Unfortunately I cannot replicate this issue. What version of zabbix do you use? Could you provide a xml dump of host causing this issue? In my case hostdump['interfaces']...

@knight42 image was built with kaniko: ``` docker run -v `pwd`/config.json:/kaniko/.docker/config.json:ro -v `pwd`/test-image:/workspace gcr.io/kaniko-project/executor:v1.3.0 --dockerfile /workspace/Dockerfile --destination r0bj/test-image:0.1 --context dir:///workspace/ ```

Just tested on 1.7.2 with the same result.

I respect your decision however I'm not 100% convinced that it's an enhancement rather than a bug. You as a user don't always have a knowledge how particular pod was...