Charly Molter
Charly Molter
Have you tried using `--kubeconfig-host` with a kubconfig for the global cluster? Seems like this should work. In any case we should update the docs to explain this
The `Values.istio.kubeconfig.secretName` istio bit is weird here :) Might be worth committing a change to rename this config in the helm chart no?
Thanks it makes sense and it's indeed a complex feature. What we've done is: `go test` for devs in their local envs to dev quickly. `ginkgo -p` in CI where...
If it's possible at all don't you think that it's likely a user would end up relying on this behavior? Should duplicates be rejected instead of relying on non deterministic...
If there's warnings in case of conflicts it's makes it obvious for user to not rely on this. /close
Triage: Yes it makes sense
I was just thinking this could be configurable through [container-patches](https://kuma.io/docs/1.8.x/explore/dpp-on-kubernetes/#custom-container-configuration). Something like: ```yaml apiVersion: kuma.io/v1alpha1 kind: ContainerPatch metadata: name: container-patch-1 namespace: kuma-system spec: initOrder: first|last| ``` or after/before container name
xref #3663
This is not something that anyone is working on atm. Kuma is an OSS project with a welcoming community we'll happily help you if you want to contribute this feature!
xref: https://github.com/kumahq/kuma/issues/2921