Open gaelleacas opened 3 years ago
I believe we don't expose the host port option through the Operator because if you had >1 Contour, the host ports would conflict between them, given that Envoy is deployed as a daemon set.
It might be nice to support host ports as an option, particularly for folks who are only creating 1 Contour instance, but we'd have to figure out the UX if there were >1 Contours.
The other option here is to use specific NodePort values for the Envoy service (https://github.com/projectcontour/contour-operator/blob/main/api/v1alpha1/contour_types.go#L282-L302), and change your KinD config to map those pre-determined nodeport values to the host (mac) on ports 80/443. Similar idea, just uses high port values instead of 80/443 in the cluster.
Hi 😃
First of all I would like to say congratz to the Contour team for all the amazing work done on Contour Project 👏 🚀
So, I'm trying Contour using Kind on Mac OS & I'm a little bit lost ([This issue helped me] (https://github.com/projectcontour/contour-operator/issues/191))
What steps did you take and what happened:
I created a new Kind Cluster with this config (expose ports 80/443):
I installed Contour following the documentation & applying this steps:
After setting foo.bar.com => localhost in my /etc/hosts When I run curl, my app is not reachable
What did you expect to happen:
curl http://foo.bar.com
Should return a code 200 with
Welcome to nginx!
html contentAnything else you would like to add:
It works very well using the Contour installation (at the step 2) doing the same steps:
I found a difference between both installation:
Contour expose pod with
hostPort
Contour Operator doesn't implement it, so we cannot add it through contour CRD Is this the desired behaviour?
I ask because I see in K8S doc
I tried to test with metallb as well but it's complex on MacOS 😫. Could be nice if we can set it in Contour CRD when we need this configuration :)
Environment:
kubectl version
):v1.21.2/etc/os-release
):macOS Big Sur 11.4