ClusterAddon created for existing cluster

Open
#109 3 comments 0 reactions 1 assignee View on GitHub

@aniruddha2000 is already working on this.

Since Mar 12, 2024.

Assessment

This issue has not been assessed yet.

Description

Container

/kind bug

What steps did you take and what happened:
I spawned CSO in the environment with an existing cluster object. This cluster is not using cluster stacks at all obviously.
I saw the ClusterAddon object created.

What did you expect to happen:
ClusterAddon is not created.

IMO it also shouldn't be created, when the cluster is not using cluster stacks.

Anything else you would like to add:
I find it during work on https://github.com/SovereignCloudStack/issues/issues/544

Environment:

  • cluster-stack-operator version: v0.1.0-alpha.3
  • Kubernetes version: v1.27.3
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.