Skip to content
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

ambassador helm chart deprecation warnings #1928

Closed
RafalSkolasinski opened this issue Jun 10, 2020 · 3 comments · Fixed by #2069
Closed

ambassador helm chart deprecation warnings #1928

RafalSkolasinski opened this issue Jun 10, 2020 · 3 comments · Fixed by #2069

Comments

@RafalSkolasinski
Copy link
Contributor

Since around last week ambassador installation renders following warning.

DEPRECATED!! This version of the chart has been deprecated.

We should verify if this requires any action from our side or is purely upstream issue.

@RafalSkolasinski RafalSkolasinski added bug triage Needs to be triaged and prioritised accordingly labels Jun 10, 2020
@RafalSkolasinski
Copy link
Contributor Author

Just on the side note: this seems to be only warning and does not cause any issues right now.

@ukclivecox ukclivecox added priority/p3 and removed triage Needs to be triaged and prioritised accordingly labels Jun 11, 2020
@RafalSkolasinski
Copy link
Contributor Author

RafalSkolasinski commented Jun 16, 2020

Seems that the new instruction should be something along these lines

kubectl create namespace ambassador || echo "namespace ambassador exists"
helm repo add datawire https://www.getambassador.io
helm install ambassador datawire/ambassador \
	--set image.repository=quay.io/datawire/ambassador \
	--set enableAES=false \
	--set crds.keep=false \
	--namespace ambassador

There is also option to set image tag --set image.tag=$version$ but not sure which version we should choose.

The --set crds.keep=false is a flag we had previously, guess we should still leave it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants