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
How to reproduce the issue Followed the official Migration lab, and using that I started the migration on my infrastructure, the command used was adapted from the lab: cilium install --helm-values values-migration.yaml --helm-auto-gen-values values-initial.yaml
Which returned the following error: unknown flag: --helm-auto-gen-values
After reading the help section from the current version of cilium-cli (one specified above), I adapted/used the following command which worked, and generated the required file: cilium install --helm-values values-migration.yaml --dry-run-helm-values values-initial.yaml > values-initial.yaml
If this behavior is normal, maybe updating the lab would be helpful, otherwise, I think a edit in the man page of cilium would help out users searching for the presumably deprecated parameter
The text was updated successfully, but these errors were encountered:
General Information
v0.15.20 compiled with go1.21.6 on darwin/amd64
kubectl server version v1.28.2+k3s1
Debian 11, k3s, kernel 5.10.0-27-amd64
How to reproduce the issue
Followed the official Migration lab, and using that I started the migration on my infrastructure, the command used was adapted from the lab:
cilium install --helm-values values-migration.yaml --helm-auto-gen-values values-initial.yaml
Which returned the following error:
unknown flag: --helm-auto-gen-values
After reading the help section from the current version of cilium-cli (one specified above), I adapted/used the following command which worked, and generated the required file:
cilium install --helm-values values-migration.yaml --dry-run-helm-values values-initial.yaml > values-initial.yaml
If this behavior is normal, maybe updating the lab would be helpful, otherwise, I think a edit in the man page of cilium would help out users searching for the presumably deprecated parameter
The text was updated successfully, but these errors were encountered: