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

Add DevContainer Definitons For One-Click Dev Env Setup #659

Open
petermetz opened this issue Apr 6, 2024 · 5 comments
Open

Add DevContainer Definitons For One-Click Dev Env Setup #659

petermetz opened this issue Apr 6, 2024 · 5 comments
Labels
needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@petermetz
Copy link

Hiya,

Just gauging interest in this before submitting a PR.
I'd be happy to contribute a dev container config [1] that makes the build setup as turn-key as it gets.

For now I'd make sure to include Bazel in it but if #587 gets completed then we can remove that.

[1] https://code.visualstudio.com/docs/devcontainers/containers

@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

If the repository mantainers determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Apr 6, 2024
@BenTheElder
Copy link
Member

Hi, thanks for the offer, I don't think this is something anyone is prepared to maintain at the moment.

There's some cleanup work ongoing and this is probably something to consider down the line.

@petermetz
Copy link
Author

Hi, thanks for the offer, I don't think this is something anyone is prepared to maintain at the moment.

There's some cleanup work ongoing and this is probably something to consider down the line.

@BenTheElder That's fair. Thank you for responding.
For when you have the bandwidth later on: I'm not a maintainer, but would be happy to keep it up to date with smaller contributions (fixing CVEs, bumping compiler versions, etc. - the mundane stuff).

@BenTheElder
Copy link
Member

Thanks!

I'm not sure to what extent I'm personally going to stay involved, for now helping escalate / coordinate some of the more pressing gaps like #686 re: cloud provider extraction, I think we're still figuring out who will handle what long term and then go from there, but I'd like to think anyone would be happy to accept help like this.

At the moment I think approvers will be a bit buried in some time-sensitive projects like #683 #686 😅, longer term personally I'd like to see enhancements to the development process etc but I can't commit yet versus existing responsibilities in the broader kubernetes project and internally ...

@petermetz
Copy link
Author

Thanks!

I'm not sure to what extent I'm personally going to stay involved, for now helping escalate / coordinate some of the more pressing gaps like #686 re: cloud provider extraction, I think we're still figuring out who will handle what long term and then go from there, but I'd like to think anyone would be happy to accept help like this.

At the moment I think approvers will be a bit buried in some time-sensitive projects like #683 #686 😅, longer term personally I'd like to see enhancements to the development process etc but I can't commit yet versus existing responsibilities in the broader kubernetes project and internally ...

@BenTheElder Got it, thank you for responding! :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
None yet
Development

No branches or pull requests

3 participants