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

Implement Containerized Testing #492

Open
jedwins1998 opened this issue Apr 2, 2024 · 6 comments
Open

Implement Containerized Testing #492

jedwins1998 opened this issue Apr 2, 2024 · 6 comments
Assignees
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@jedwins1998
Copy link
Contributor

The current testing setup requires a user to perform a lot of setup on their bare metal machine for everything to work. It would be a nice improvement if all the setup could be done in a container that users could pull to perform their testing.

@jedwins1998
Copy link
Contributor Author

/assign

@kannon92
Copy link
Contributor

kannon92 commented Apr 2, 2024

❤️

@jedwins1998
Copy link
Contributor Author

@kannon92
Copy link
Contributor

kannon92 commented Apr 8, 2024

I really want a devcontainer and I tried to bring it up kubernetes-sigs/kubebuilder#3432 here.

Mostly I was hoping that one could use kubebuilder, generate the code and have at least a template for devcontainers/devpods.

I don't have that much experience in this area but that would be my wishlist.

I think e2e tests are difficult as kind doesn't support that AFAIK. But that could be one area to explore.

@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 7, 2024
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle rotten
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Aug 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

4 participants