Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[WIP] Devcontainers v2 #398

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

Gregory-Pereira
Copy link
Collaborator

@Gregory-Pereira Gregory-Pereira commented Dec 8, 2024

Changes:

  • install kubectl, kubeseal, docker and kind into the devcontainer
  • bind mount the docker socket to devcontainer giving it access to host docker instance
  • [WIP] enabling kind cluster creation, deletion, and manipulation seamlessly from both devcontainer and host machine, or a mix therof
  • install zsh and oh-my-zsh for syntax highlighting, above binary completions, and general DevX. Also setting it as the default shell
  • changing the kind related make targets to be deploy-kind, undeploy-kind, etc. This keeps the naming conventions consistent with how the openshift prod and qa envs are named.

Signed-off-by: greg pereira <[email protected]>
@Gregory-Pereira Gregory-Pereira force-pushed the devcontainer-kube-related-improvements branch from 7c3c9f3 to 2cf7ba4 Compare December 8, 2024 18:40
@Gregory-Pereira
Copy link
Collaborator Author

Gregory-Pereira commented Dec 8, 2024

Could use some networking help from the experts @nerdalert and @vishnoianil. Inside the container it can see itself as well as other pre-provisioned kind cluster nodes, however when I try to make a kind cluster from within the container it gives me port refusal: The connection to the server 127.0.0.1:6443 was refused - did you specify the right host or port?. I bound this to 6443 in the networking section of the instructlab-ui kind cluster we have because I need some way of sharing access to the kind kubernetes API to the devcontainer, and by default it just picks a random port. Is a Proxy for the kube API the right answer here? I see there are some options for that: https://pkg.go.dev/sigs.k8s.io/kind/pkg/apis/config/v1alpha4#Networking. I think I get what the problem is, I just dont know how to solve it.

Signed-off-by: greg pereira <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant