search

stakater / IngressMonitorController

A Kubernetes controller to watch ingresses and create liveness alerts for your apps/microservices in UptimeRobot, StatusCake, Pingdom, etc. – [✩Star] if you're using it!
https://stakater.com
Apache License 2.0
600 stars 104 forks source link

How to deal with newer Ingress Controllers that use CRDs instead of Ingress resource? #227

Open Yggdrasil opened 4 years ago

Yggdrasil commented 4 years ago

The newer versions of Nginx and Traefik ingress controllers have switched to using CRDs (Custom Resource Definition) instead of the common Ingress resource.

This is because the Ingress resource is not flexible enough to deal with more complex routing requirements. It appears the Kubernetes developers agree that moving to custom resources is the path forward, instead of expanding the Ingress definition with ever more annotations.

Here's an example of Traefik 2.0's implementation: the IngressRoute resource.

Have you considered this change? How do you plan to get the fqdn from these CRDs?

rasheedamir commented 4 years ago

@Yggdrasil we have a plan to change IMC to CRD as well!

PR will be very welcome! would you like to write one?

github-actions[bot] commented 1 year ago

This issue is stale because it has been open for 60 days with no activity.

github-actions[bot] commented 1 year ago

This issue was closed because it has been inactive for 30 days since being marked as stale.

karl-johan-grahn commented 1 year ago

Reopening issues that inadvertently were closed as stale