Closed ShurikAg closed 2 years ago
Hi @ShurikAg it is possible to provide us the following informations: helm version
, helm ls -n ambassador
and kubectl get nodes
after you run the installation command ?
On the official Ambassador repository the following issue https://github.com/emissary-ingress/emissary/issues/4031 has been raised for a similar concern
helm version
version.BuildInfo{Version:"v3.7.2", GitCommit:"663a896f4a815053445eec4153677ddc24a0a361", GitTreeState:"clean", GoVersion:"go1.17.3"}
helm ls -n ambassador
NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION
ambassador ambassador 2 2022-01-21 01:37:55.045387 -0800 PST deployed ambassador-6.9.3 1.14.2
kubectl get nodes
NAME STATUS ROLES AGE VERSION
priz-prod-usnb3 Ready <none> 28h v1.21.5
priz-prod-usnb8 Ready <none> 28h v1.21.5
Hi @ShurikAg thank you for the details, the same versions have been used in our validation and the installation of the component was without any issue. The warnings from the installation can be ignored and from what we can see the support for ambassador-ingress is no longer supported.
We have raised the following issue https://github.com/digitalocean/Kubernetes-Starter-Kit-Developers/issues/115 for upgrading the ambassador-ingress to emissary-ingress in order to support the current k8s version 1.21 but also the new ones that will be released
Hi @ShurikAg we have added Ambassador 2.x in the StarterKit , we recomand to use it. The Ambassador 1.x is obsoleted
Thanks for the starter kit, that is exactly what I needed. I am following the instructions and when trying to install the Ambassador
I am getting a bunch of deprecation warnings.
Is it expected? Can it be fixed?
The last message worries me more. I did not have any other instances of ambassador before the installation, and yet, there is a warning about an existing one.