Pablo Chico de Guzman
Pablo Chico de Guzman
Exposing services using ingress/routes is a very common scenario in production environments today. I think having support for them is a need to make Compose more powerful in production environments....
@ndeloof the port in the endpoint definition matches the port in the service definition. If the ports don't match, we throw an error
Normally you already have an ingress controller in your cluster listening in a public port, and the developer doesn't have control over it, it is configured by the ops team....
Tests are all passing. Everything looks good but the certificate.
@mohamed-taman any update on this issue? or guidance on how to solve it?
@mohamed-taman I am trying to run the app on Kubernetes, behind an nginx ingress controller that provides HTTPs termination. Is it possible to expose the gateway on HTTP?
@mohamed-taman :popcorn:
+1 for implementing support for different namespaces. We would need something like this: ``` kind: TrafficSplit metadata: name: ab-test spec: service: website matches: - kind: HTTPRouteGroup name: ab-test backends: -...
@nicholasjackson sure. I am one of the founders of Okteto. Okteto is a development platform on top of Kubernetes. Our vision is that every developer should have her own namespace...
Fixed here https://github.com/okteto/okteto/pull/3133