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

Update lab 3 #940

Open
aburdenthehand opened this issue Mar 22, 2024 · 5 comments
Open

Update lab 3 #940

aburdenthehand opened this issue Mar 22, 2024 · 5 comments
Labels
hacktoberfest Categorizes as a Hacktoberfest contribution kind/bug

Comments

@aburdenthehand
Copy link
Contributor

It looks like our KubeVirt labs are out of date :(
It would be great if someone could run through the labs and update the guide accordingly. This is an opportunity to also increase the amount of information if need be.

Github link: https://github.com/kubevirt/kubevirt.github.io/blob/main/labs/kubernetes/lab3.md
Website link: https://kubevirt.io/labs/kubernetes/lab3.html

Now that we're on a slower release cadence, we should be able to update these labs on an annual basis, tied to the most recently released version, which will be supported for ~12 months. Running and updating the labs could be a useful exercise for new contributors, provided they are supported if and when they need to troubleshoot changes in the procedure.

@kubevirt-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@kubevirt-bot kubevirt-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 20, 2024
@kubevirt-bot
Copy link
Contributor

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

@kubevirt-bot kubevirt-bot 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 Jul 20, 2024
@kubevirt-bot
Copy link
Contributor

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

@kubevirt-bot
Copy link
Contributor

@kubevirt-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

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.

@aburdenthehand aburdenthehand reopened this Oct 2, 2024
@aburdenthehand
Copy link
Contributor Author

/remove-lifecycle rotten

@kubevirt-bot kubevirt-bot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Oct 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
hacktoberfest Categorizes as a Hacktoberfest contribution kind/bug
Projects
None yet
Development

No branches or pull requests

2 participants