-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Please sync the Ambassador Edge Stack version with the Helm CHART/APP VERSION #68
Comments
Some context around the artifacthub link might help: the link we generate for the new chart version of every release includes the main helm chart readme as it was at the time that the release went out, so if you perhaps ran the below straight from that page:
it would install the latest version (3.0) because the version isn't specified in those commands. (The readme does not get updated with every chart version - it just shows how the install command works.) That page may be a bit confusing, but there is an Install button which, if you click, will generate the correct helm command: Note that editing the image tag alone isn't recommended as other potential yaml/chart changes won't be incorporated and may lead to incompatibilities. In our testing, In trying different install approaches, might you perhaps have both versions installed such that you're getting that v3.0 / Helm 8.0.0 output when running that helm command? |
Upgrades are coming soon so I need to install a specific version of AES:
2.1.1
, then upgrade to the latest from there.No matter what is done, this seems to be the result:
Used the CRDs for that version:
https://app.getambassador.io/yaml/edge-stack/2.1.1/aes-crds.yaml
Since this is not latest version of
aes
, it appears I need to install from the official Helm repo so I can specify a version. I've selected Helm chartv7.2.1
, which should deployAPPLICATION VERSION 2.1.1
.When that didn't work, I downloaded/pointed to a values file that specifies:
After spending way too much time on this, I finally exec'd into the shell for one of the deployed containers:
It was installing the correct version all along.
Please fix this :-)
The text was updated successfully, but these errors were encountered: