kubevirt / kubevirt.github.io

KubeVirt website repo, documentation at https://kubevirt.io/user-guide/
https://kubevirt.io
MIT License
29 stars 109 forks source link

Add instancetype.kubevirt.io/v1beta1 update post #908

Closed lyarwood closed 4 months ago

lyarwood commented 1 year ago

What this PR does / why we need it:

Adds a instancetype.kubevirt.io/v1beta1 update blog post based on a personal blog post I've written below :

https://blog.yarwood.me.uk/2023/06/22/kubevirt_instancetype_update_5/

Does this PR fix any issue? _(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged)_:

Fixes #

Special notes for your reviewer:

kubevirt-bot commented 1 year ago

Skipping CI for Draft Pull Request. If you want CI signal for your change, please convert it to an actual PR. You can still manually trigger a test run with /test all

lyarwood commented 1 year ago

I have just a few comments, mostly for possible clarification. All can probably be safely ignored.

I like the blog post, very informative and written for easy understanding.

Thanks, I'll clean this up tomorrow. FWIW this is based on the following personal blog post, I've dropped the bugfix section as I'm not sure how useful that would be in this particular blog:

https://blog.yarwood.me.uk/2023/06/22/kubevirt_instancetype_update_5/

lyarwood commented 11 months ago

@jobbler @cwilkers I forgot to follow up with this after the v1.0.0 release, do you think this can be published now?

lyarwood commented 9 months ago

/close

kubevirt-bot commented 9 months ago

@lyarwood: Closed this PR.

In response to [this](https://github.com/kubevirt/kubevirt.github.io/pull/908#issuecomment-1713418472): >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
lyarwood commented 9 months ago

/reopen

kubevirt-bot commented 9 months ago

@lyarwood: Reopened this PR.

In response to [this](https://github.com/kubevirt/kubevirt.github.io/pull/908#issuecomment-1722977532): >/reopen Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
kubevirt-bot commented 9 months ago

[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 davidvossel for approval. For more information see the Kubernetes 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](https://github.com/kubevirt/kubevirt.github.io/blob/main/OWNERS)** Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment
kubevirt-bot commented 6 months ago

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 commented 5 months ago

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 commented 4 months ago

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

/close

kubevirt-bot commented 4 months ago

@kubevirt-bot: Closed this PR.

In response to [this](https://github.com/kubevirt/kubevirt.github.io/pull/908#issuecomment-1951450371): >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](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.