github-actions[bot]
commented
1 year ago The Contour project currently lacks enough contributors to adequately respond to all Issues.
This bot triages Issues according to the following rules:
- After 60d of inactivity, lifecycle/stale is applied
- After 30d of inactivity since lifecycle/stale was applied, the Issue is closed
You can:
- Mark this Issue as fresh by commenting
- Close this Issue
- Offer to help out with triage
Please send feedback to the #contour channel in the Kubernetes Slack
skriss
When Contour is dynamically provisioned by the Gateway Provisioner, the Provisioner acts as the reconciler for Gateway Listeners, and adjusts the Envoy Service spec as needed to expose the proper ports. However, when Contour is statically provisioned, there is no Gateway Provisioner in the picture, so the user must manually keep the Envoy Service spec in sync with the Gateway Listeners.
We've discussed in the past allowing Contour to manage the Envoy Service spec in this scenario. I think this is worth revisiting, as it is technically feasible and would eliminate a point of friction for folks who want to statically provision Contour, but still want the benefit of dynamic Gateway Listeners.