kubernetes-sigs / kubernetes-sigs/cluster-api-provider-cloudstack
CloudStack Sync with ACS is broken
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 45
- Forks
- 38
- PR merge metrics
- No merged PRs in 30d
Description
/kind bug
What steps did you take and what happened:
Enabling CLOUDSTACK_SYNC_WITH_ACS is buggy and will add multiple VMs that are not part of the K8s cluster to the Kubernetes tab in CloudStack.
What did you expect to happen:
CLOUDSTACK_SYNC_WITH_ACS should only add VMs and Firewall Rules related to the Workload cluster created by CAPC.
Environment:
- Cluster-api-provider-cloudstack version: v0.6.1
- Kubernetes version: v1.32.3
- OS: Rocky Linux 9
- ACS version: 4.22.0
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.
Research direction
Start by locating the CLOUDSTACK_SYNC_WITH_ACS handling and reproduce the issue with Cluster-api-provider-cloudstack v0.6.1 against Apache CloudStack 4.22.0. Trace how VMs and firewall rules are selected for synchronization, then verify that only resources belonging to the CAPC workload cluster appear in the Kubernetes tab.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100