replicatedhq / replicatedhq/kURL
Failed to connect remotely to the k8s cluster using kubectl
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 809
- Forks
- 81
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 20
Description
Observed in Azure kurl installation, sudo bash tasks.sh generate-admin-user put the private IP of the cluster instead of the public one.
Thus the generated kube config cannot be used outside of the machine.
To reproduce, create an Azure VM and install a k8s cluster using kurl. Follow https://kurl.sh/docs/install-with-kurl/connecting-remotely to connect remotely.
Expected: able to connect.
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
Reproduce the issue by following the Azure VM and remote-connection steps in the linked kURL documentation, then inspect tasks.sh at generate-admin-user. Verify which cluster address is placed in the generated kube config; done means the config uses an externally reachable address and kubectl can connect from outside the VM.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, bash, shell
- Domain
- cli, cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100