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

Multi-stage cluster addons: Wrong clusterstack name in debug logs

Open
  • Is something wrong?
#213 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
go
Domain
devops

Research direction

Start by tracing the debug logging and update calls that read the clusterstack from the spec. Compare those reads with cluster.spec.topology.class, which the issue identifies as the authoritative value. Done means debug logs consistently show the cluster stack name from that field, including during updates.

Written by the indexing model from the issue text.

Description

Container

/kind bug

What steps did you take and what happened:
Currently, we reference the clusterstack from the spec, but it is either outdated (in update calls) or empty.

What did you expect to happen:
We should use the one specified in cluster.spec.topology.class

Dominant language
Go
Stars
18
Forks
5
No merged PRs in 30d

Getting set up

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.