✨ Initial devcontainer support

[faermanj]

/kind support

Adding .devcontainer with clusterctl, kind and other dependencies.

NONE

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign richardcase for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-ci-robot]

Hi @faermanj. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[richardcase]

/ok-to-test

[richardcase]

Thanks for this @faermanj . Can we simplify this by using an existing base image and features?

For example:

{
	"name": "CPAA",
	// Or use a Dockerfile or Docker Compose file. More info: https://containers.dev/guide/dockerfile
	"image": "mcr.microsoft.com/devcontainers/go:1-1.22-bookworm",
	// Features to add to the dev container. More info: https://containers.dev/features.
	"features": {
		"ghcr.io/devcontainers/features/docker-in-docker:2": {},
		"ghcr.io/devcontainers-contrib/features/kind:1": {},
		"ghcr.io/rio/features/k9s:1": {},
		"ghcr.io/devcontainers/features/kubectl-helm-minikube:1": {
			"version": "latest",
			"helm": "latest",
			"minikube": "none"
		}
	},
	// Configure tool-specific properties.
	"customizations": {
		"vscode": {
			"extensions": [
				"ms-kubernetes-tools.vscode-kubernetes-tools",
				"ms-azuretools.vscode-dockerr",
				"golang.go"
			]
.....

Whats the benefit to using a container file? We could also use devbox within the devcontainer.

[faermanj]

@richardcase Sure, i'll try the devbox devcontainer then, if kind works in that it should be fine.

[faermanj]

• Changed to kind feature instead of dockerfile scripts
• Changed to go latest base image
• Integrated devbox

[richardcase]

@faermanj - thanks for considering the change. I think this is simpler, plus people can then use devbox locally if they want.

Have you seen the devbox generate devcontainer command by the way? It would reduce the need for the devbox feature and postCreateCommand i think.

[faermanj]

@faermanj - thanks for considering the change. I think this is simpler, plus people can then use devbox locally if they want.

Have you seen the devbox generate devcontainer command by the way? It would reduce the need for the devbox feature and postCreateCommand i think.

I did, and started from that. However, kind failed to create the cluster so I added the features and it worked \o/

[k8s-ci-robot]

Adding label do-not-merge/contains-merge-commits because PR contains merge commits, which are not allowed in this repository.
Use git rebase to reapply your commits on top of the target branch. Detailed instructions for doing so can be found here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.