Kubernetes ingress controller

[sergelogvinov]

Hello, thank you for the great project!

Do you have any plans to implement an ingress controller that automatically downloads TLS secrets for domains and maintains the upstream configuration?

Or would it be better to implement this as a separate sidecar controller?

Thanks.

[sadoyan]

Hello,

Thanks for suggestion . Currently it have kind of integration with Kuberenetes api and can pull upstreams automatically .
Can you please give more details about your idea ? What you means by saying "automatically downloads TLS secrets for domains" ?
Please give some more details .

Thanks

[sergelogvinov]

Hello, based on the documentation, Aralez watches Kubernetes Service endpoints and dynamically updates the backend IPs. https://sadoyan.github.io/aralez-docs/assets/kubernetes/

The list of services and domains need to be configured in upstreams.yml.

So we need to update upstreams.yml manually. Normally, an Ingress controller watches ingress resources and automatically updates the list of domains, certificates and service list.

[sadoyan]

You need to update the upstreams.yml just to set names.
hostname: which is hostname used to access the proxy server
upstream: the service name, from where Aralez will go and get the real list of upstreams and automatically update its routing, once the list is changed .
Regarding watching secrets for certificate changes . Good idea , will implement