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
Add Codespaces configuration dev container #113019
Comments
@craiglpeters: The label(s) In response to this:
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/test-infra repository. |
/sig contributor-experience |
We had a discussion on permission based issues regarding enabling code spaces for k/k, I think it would be better to run it through SIG-Infra once to see how can we set it up for k/k, because at the moment building kubernetes on code spaces base tier isn't possible yet. |
@Debanitrkl can you help me understand what you mean? I am currently testing building kubernetes in a default codespace and haven't faced any issues yet. |
AFAIK we don't need to do any permissions change to create a default code space. We don't have to configure it so spinning things up would come out of the orgs allocation. |
I was trying out the the |
Also, since it directly spins-up a development environment, we need to have the pre-requisite environment configuration defined in devcontainer.json, but since that may vary for different use cases are we planning to have all the pre-requisites to be set-up by default in the environment. |
Presently these all tests fail for less disk space on running
|
@Debanitrkl it seems that you are using a machine with too few resources. It may be the case that you don't (yet) have access to larger machines. Soon everyone will have access to larger machines, but I can help you get access to a larger machine to test on now. |
Update: I tested with a 4 core codespace and could |
I would also hope for gitpod |
We'd accept a gitpod config, but would need someone to take ownership of maintaining it. |
/triage accepted |
cc: @pymander |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
This seems to have moved beyond just a config file in the repo: kubernetes/test-infra#30454 (comment), kubernetes/org#4468 |
@BenTheElder Just to be clear - I think support for devcontainers can come in many forms, based on speed to launch, complexity and reliability. Depending on how Kubernetes would like "per-repo" tools to work, the implementation can change. |
What would you like to be added?
For contributors to Kubernetes, a configuration to assure that Codespaces will work with Kubernetes will enable the use of a cloud-based development environment to easily provision an environment with all the requirements and dependencies automatically installed and configured. This will make life easy for new and existing contributors when they are working on multiple branches with different dependencies, or don't have access to a computer or network powerful enough to build Kubernetes.
The Codespaces configuration consists of a Development Container (devcontainer) file
devcontainer.json
which encodes the configuration of the environment.Why is this needed?
sig/contribex is working on a new self-paced course for Kubernetes contribution to be hosted on k8s.dev. Codespaces will be one option for working through the course material
cc: @mrbobbytables
The text was updated successfully, but these errors were encountered: