sync helm version to omit different behavior

Open
#216 0 comments 0 reactions 0 assignees View on GitHub

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

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

Container

/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

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from SovereignCloudStack/cluster-stack-operator

All issues in SovereignCloudStack/cluster-stack-operator

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.