crabique
crabique
I think this one is closed by the same PR as the #3422
For `SecureString` it would also require specifying the encryption KMS key ID for cases where a non-default key should be used.
Does this imply completions on kubectl-command level (namespaces etc) or for subcommands as well, e.g. for `rook-ceph rbd`?
Not sure if related, but there is inconsistent behaviour in terms of plugins output renderer not respecting the TTY: ```bash ❯ kubectl get secret test --template '{{ base64decode .data.pass }}'...
There's #117 with some rabbit holes into kustomize issues, but it seems this particular issue was never explicitly raised upstream. That said, I agree it's a real issue with my...
I guess this is no longer relevant in context of https://github.com/travisghansen/argo-cd-helmfile/issues/71
You could use the `postRenderer` Helm feature and feed the entire stdout of `helmfile template` into a kustomize wrapper.
This is a problem even without `force-update` as ArgoCD Application resource exports _all_ images owned by the managed resources, so for a cronjob this means: - argocd-image-updater sees the exported...
@mmontes11 would it make sense to set the labels by the controller directly? Since it already watches pods and knows each pod's role, can't the labels be applied to all...
I agree. Especially now that Helmfile `v1.0.0` with some breaking changes is about to be released, logically this would require a major version bump for the plugin as well, and...