sync helm version to omit different behavior
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- helm, kubernetes
- Domain
- devops, infrastructure
Research direction
Start by searching the repository for Helm version references and the Renovate and Tilt configuration mentioned in the issue. Compare the versions used for the image and local development paths; done means both paths use the same Helm version and produce the same outcome.
Written by the indexing model from the issue text.
Description
/kind bug
What steps did you take and what happened:
[A clear and concise description of what the bug is.]
bumping helm version without testing can lead to problem and we should have it synchronized. As of now renovate bumps it and this leads to different outcome in cso image usage and local development usage with tilt version. This issue tracks having the version synchronized across the repository.
What did you expect to happen:
Have same outcome when using helm using image as well as using Tilt for local development.
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Environment:
- cluster-stack-operator version:
- Kubernetes version: (use
kubectl version) - OS (e.g. from
/etc/os-release):
- Dominant language
- Go
- Stars
- 18
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
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.
More from SovereignCloudStack/cluster-stack-operator
-
CI issues (1) Openbug Container
SovereignCloudStack/cluster-stack-operator#340 · 1 comment · 3 assignees ·
-
cso: crash .... Open
Difficulty 3/5 1-2 days Newbie friendliness 58/100
SovereignCloudStack/cluster-stack-operator#337 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 50/100
SovereignCloudStack/cluster-stack-operator#336 · 3 comments ·
-
bug
SovereignCloudStack/cluster-stack-operator#327 · 1 assignee ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
SovereignCloudStack/cluster-stack-operator#272 · 32 comments ·
All issues in SovereignCloudStack/cluster-stack-operator
Similar issues
-
kind/bug needs-triage
Difficulty 1/5 Under an hour Newbie friendliness 72/100
matrixorigin/matrixone#29223 ·
-
needs-acceptance wg/data-plane-networking
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
vllm-project/semantic-router#4024 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
alexgorbatchev/dotfiles#107 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100