You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to be able to inject the ingress configuration that is usually gathered from static annotations instead through a configmap. I am happy to look into implementing this myself if this would be an acceptable addition. I was hoping in the ingress I could write:
This would allow me to reuse the same declarative Gitops repo and simply terraform a new cluster and static IP, then have terraform inject the IP name as config.
The text was updated successfully, but these errors were encountered:
@olib963 I'm not sure your proposal makes sense. IIUC, this would require a change to the Ingress API to support the "configMapName" field? This is definitely a non-starter.
@rramkumar1 That's ok, we could have added this functionality in an annotation instead of in the spec field e.g. gce.ingress/configmap: ingress. I have decided to go with the NGINX ingress instead, it seems a little more mature and configurable and isn't leaking resources as we rebuild. Thank you for the reply :D
I would like to be able to inject the ingress configuration that is usually gathered from static annotations instead through a configmap. I am happy to look into implementing this myself if this would be an acceptable addition. I was hoping in the ingress I could write:
where the configmap is
This would allow me to reuse the same declarative Gitops repo and simply terraform a new cluster and static IP, then have terraform inject the IP name as config.
The text was updated successfully, but these errors were encountered: