linode / linode/linode-cloud-controller-manager
Deployment not fit for production use
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 94
- Forks
- 75
- Avg merge
- 11h 19m
- Merged PRs (30d)
- 20
Description
I noticed, that generated CCM deployment use latest tag, this disallow use it in production clusters. You should use versioning with compatibility table (ccm version - k8s compatible versions).
Many companies won't use managed k8s solution and preffer do deploy k8s by itself.
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
Start by locating the generated CCM deployment that currently uses the latest tag and identify where Kubernetes compatibility is documented or configured. Done means the deployment uses a versioned CCM image and a compatibility table maps CCM versions to supported Kubernetes versions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100