Add documentation for AKS specific configuration
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 60
- Forks
- 221
- Avg merge
- 4h 32m
- Merged PRs (30d)
- 1
Description
If you are using AKS, it would be best to exclude kube-system / tunnelfront from the MWC (if using --ha). When tunnelfront is not scheduled, the api-server cannot talk to the proxy-injector, and if the api-server is trying to reschedule tunnelfront, the system will be stuck in this bad state forever.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no file or test; start by locating the website's AKS or MWC configuration documentation. Done means documenting that AKS users with --ha should exclude kube-system/tunnelfront from the MWC and explaining the failure mode when tunnelfront is unscheduled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, kubernetes
- Domain
- cloud, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100