`oci ce cluster create-kubeconfig` does not preserve some keys after "merging"
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 669
- Forks
- 236
- Avg merge
- 1m
- Merged PRs (30d)
- 4
Description
I am losing some convenient attributes in my kubeconfig everytime I need to reauth, which is quite often; and is annoying
right now, existing entries with the same name are intentionally replaced, so if I have
clusters:
- cluster:
certificate-authority-data: xyz
proxy-url: socks5://localhost:1080
server: https://1.2.3.4:6443
name: cluster-xyz
contexts:
- context:
cluster: cluster-xyz
user: user-xyz
namespace: my-service
name: context-xyz
I lose proxy-url: socks5://localhost:1080 and namespace: my-service even when the msg says
Existing Kubeconfig file found at ~/.kube/config and new config merged into it
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 at the oci ce cluster create-kubeconfig command and trace the kubeconfig merge behavior when an existing entry has the same name. Reproduce the issue with the YAML example, then verify that reauthentication preserves proxy-url and namespace while still updating the generated configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, python
- Domain
- cli, cloud
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100