contour
contour copied to clipboard
projectcontour
Generate config file documentation
To ensure that the Contour configuration file documentation is always up to date, we should generate it from code comments in the Contour source.
Agreed. Ideally it comes from some config system or CI/CD pipeline so we have full audit capabilities, know who made what changes and can tie this back to the specific release with a little bit of effort. If user deploys an older version of Contour, they can also grab the older config file that goes with it. This is not critical for us though, but it’d be a nice bonus
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
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
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