[ROSAENG-16042] osdctl break glass cleanup fails for GCP PSC clusters
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 47
- Forks
- 142
- Avg merge
- 21h 19m
- Merged PRs (30d)
- 9
Description
The osdctl cluster break glass cleanup command does not properly clean up resources for PSC (Private Service Connect) clusters. Resources need to be manually cleaned up instead.
Steps to Reproduce
- Break-glass to a PSC cluster - similar to a Privatelink cluster this will create a pod on the hive as only connections from hive IPs are accepted.
The cleanup command should delete this Pod again, but instead only prints the logs that it did unset the KUBECONFIG variable (non-privatelink behavior).
Contributor guide
No contributing guide indexed for this repository
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 with the osdctl cluster break glass cleanup command and reproduce the failure against a GCP PSC cluster. Compare the PSC path with the Privatelink behavior, focusing on whether the break-glass pod is deleted rather than only logging that KUBECONFIG was unset; done means the pod and related resources are cleaned up automatically.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- gcp, go, kubernetes
- Domain
- cli, cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100