Skip to content

feat: fallback ingress support#37

Draft
justinrubek wants to merge 4 commits into
mainfrom
non-istio-ingress
Draft

feat: fallback ingress support#37
justinrubek wants to merge 4 commits into
mainfrom
non-istio-ingress

Conversation

@justinrubek

Copy link
Copy Markdown

Adds support for using a kubernetes ingress in place of an istio gateway depending on an annotation. This can be used to solve chicken and egg problems when migrating a domain to istio without breaking routing during the migration. The annotation value denotes that DNS is not pointed to istio and that the gateway will not receive traffic. Instead of creating a virtualservice, the gateway controller will create an ingress that routes to the challenge solver service. Additionally, an orderwatcher controller watches orders for resolution and emits events. This can be used to detect when a certificate has been solved.

Support for creation of a kubernetes ingress in place of a gateway when
it is known that DNS does not route to the gateway detected by the
gateway controller. DNS activity is detected by looking at a given
annotation on the gateway resource that determines if dns is disabled.
This controller watches orders for those that are created by the gateway
controller creating a certificate. When these orders resolve it emits
kubernetes events so that certificate resolution can be detected and
actioned on.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant