Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Remove helmchartstatus after hook is finished

Open
#138 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
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
go, helm, kubernetes
Domain
devops, infrastructure

Research direction

The issue names no files, tests, or entry points. Start by tracing where hook completion updates the cluster addon status and how helm chart status is read by the next hook. Done means the status is reset after a hook finishes so the following hook starts with fresh status.

Written by the indexing model from the issue text.

Description

Container

/kind feature

Describe the solution you'd like
Once a hook is finished we should reset the status of helm charts in the cluster addon status and next hook should have fresh status to track things

Environment:

  • cluster-stack-operator version:
  • Kubernetes version: (use kubectl version)
  • OS (e.g. from /etc/os-release):
Dominant language
Go
Stars
18
Forks
5
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.