-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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 Addon fails to start #10093
Comments
This seems to be a configuration issue with our ambassador addon yaml. This addon was contributed by the community, so the minikube maintainers can't guarantee being able to maintain these properly. We will happily review any PRs to fix this though. |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-contributor-experience at kubernetes/community. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-contributor-experience at kubernetes/community. |
Freezing this so it doesn't accidentally get closed. Help still wanted! |
@sharifelgamal, it seems Ambassador has been renamed to "emissary-ingress" https://www.cncf.io/blog/2021/04/13/emissary-ingress-formerly-ambassador-is-now-a-cncf-incubating-project/ so maybe this issue needs to be redefined. |
Steps to reproduce the issue:
Enabling the Ambassador-Addon does work, however the 3 Pods (not the ambassador-operator) won´t start properly. Instead they log the following message over and over:
Pod-Log:
E0105 16:48:22.689662 1 reflector.go:178] k8s.io/client-go@v0.18.4/tools/cache/reflector.go:125: Failed to list *unstructured.Unstructured: ingressclasses.networking.k8s.io is forbidden: User "system:serviceaccount:ambassador:ambassador" cannot list resource "ingressclasses" in API group "networking.k8s.io" at the cluster scope
It seems as if the problem is caused by the new Ambassador-Version (1.10.0). In Version 1.9.1 everything works fine.
Full Pod-Log:
Running Pods:
Addons which are also enabled:
Specs:
Driver: Parallels
CPUs: 12
RAM: 12GB
Disk: 30GB
OS: macOS 11.1
Confirmend the error also exists with the docker driver.
The text was updated successfully, but these errors were encountered: