-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Gateway API doc issues #12630
Comments
Does it make sense to at least update the for==condition? |
The initial command that failed also has the same error against an IKS cluster I created. |
Strange that minikube didn't have the error when installing the crds. That implies it already had them, so the question is what version? The fact that the wait for condition=ready isn't working, implies that the gateway isn't coming up (maybe related to the wrong installed CRD version in the cluster). You can check |
|
So looks like I'll close this for now as this is working once the EXTERNAL-IP gets set. |
Gateway API requires external loadbalancer, so you MUST use minikube tunnel, but even there minikube isn't great because you can only have one loadbalancer-type service, so if you already have a gateway (gateway-api or plain Istio), a second one won't work (or it steals the LB and the first one stops working). Bottom line is that minikube isn't the best env for Gateway API. Also kind will absolutely need MetalLB installed (which doesn't work on a Mac). |
First tried with kind clusters (various k8s versions) and run into an issue with:
The command works fine against a minikube cluster.
Continuing onward with minikube, this command is failing for me
The gateway is there:
I notice:
works.
The text was updated successfully, but these errors were encountered: