Skip to content

Conversation

@jeana-redhat
Copy link
Contributor

@jeana-redhat jeana-redhat commented Jan 19, 2026

Version(s):
4.21+

Issue:
OSDOCS-17764 / OSDOCS-15747

Link to docs preview:
Creating Spot VMs by using compute machine sets

QE review:

  • QE has approved this change.

Additional information:

@jeana-redhat jeana-redhat added this to the Planned for 4.21 GA milestone Jan 19, 2026
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jan 19, 2026
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 19, 2026

@jeana-redhat: This pull request references OSDOCS-15747 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the epic to target either version "4.22." or "openshift-4.22.", but it targets "openshift-4.21" instead.

Details

In response to this:

Version(s):
4.21+

Issue:
OSDOCS-15747

Link to docs preview:

QE review:

  • QE has approved this change.

Additional information:
Unclear if these docs should replace the preemptible VM docs or coexist as an addition. Both are supported, but Spot VMs are recommended now by the cloud provider instead. Drafted content side-by-side until I hear back from dev on that question.

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 openshift-eng/jira-lifecycle-plugin repository.

1 similar comment
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 19, 2026

@jeana-redhat: This pull request references OSDOCS-15747 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the epic to target either version "4.22." or "openshift-4.22.", but it targets "openshift-4.21" instead.

Details

In response to this:

Version(s):
4.21+

Issue:
OSDOCS-15747

Link to docs preview:

QE review:

  • QE has approved this change.

Additional information:
Unclear if these docs should replace the preemptible VM docs or coexist as an addition. Both are supported, but Spot VMs are recommended now by the cloud provider instead. Drafted content side-by-side until I hear back from dev on that question.

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Jan 19, 2026
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 19, 2026

@jeana-redhat: This pull request references OSDOCS-15747 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the epic to target either version "4.22." or "openshift-4.22.", but it targets "openshift-4.21" instead.

Details

In response to this:

Version(s):
4.21+

Issue:
OSDOCS-15747

Link to docs preview:
Creating Spot VMs by using compute machine sets

QE review:

  • QE has approved this change.

Additional information:
Unclear if these docs should replace the preemptible VM docs or coexist as an addition. Both are supported, but Spot VMs are recommended now by the cloud provider instead. Drafted content side-by-side until I hear back from dev on that question.

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 19, 2026

@jeana-redhat: This pull request references OSDOCS-15747 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the epic to target either version "4.22." or "openshift-4.22.", but it targets "openshift-4.21" instead.

Details

In response to this:

Version(s):
4.21+

Issue:
OSDOCS-17764 / OSDOCS-15747

Link to docs preview:
Creating Spot VMs by using compute machine sets

QE review:

  • QE has approved this change.

Additional information:
Unclear if these docs should replace the preemptible VM docs or coexist as an addition. Both are supported, but Spot VMs are recommended now by the cloud provider instead. Drafted content side-by-side until I hear back from dev on that question.

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 26, 2026

@jeana-redhat: This pull request references OSDOCS-15747 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the epic to target either version "4.22." or "openshift-4.22.", but it targets "openshift-4.21" instead.

Details

In response to this:

Version(s):
4.21+

Issue:
OSDOCS-17764 / OSDOCS-15747

Link to docs preview:
Creating Spot VMs by using compute machine sets

QE review:

  • QE has approved this change.

Additional information:

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 openshift-eng/jira-lifecycle-plugin repository.

@jeana-redhat jeana-redhat force-pushed the OSDOCS-15747-gcp-spot-vm-mapi branch 2 times, most recently from e222fb0 to a3e1ae2 Compare January 26, 2026 19:35
@jeana-redhat jeana-redhat force-pushed the OSDOCS-15747-gcp-spot-vm-mapi branch 2 times, most recently from f101525 to aadc6be Compare January 28, 2026 17:16
@openshift-ci openshift-ci bot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Jan 28, 2026
@jeana-redhat jeana-redhat force-pushed the OSDOCS-15747-gcp-spot-vm-mapi branch 3 times, most recently from bdc1037 to 0c600ad Compare January 28, 2026 17:23
@jeana-redhat jeana-redhat added the merge-review-needed Signifies that the merge review team needs to review this PR label Jan 28, 2026
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 28, 2026

@jeana-redhat: This pull request references OSDOCS-15747 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the epic to target either version "4.22." or "openshift-4.22.", but it targets "openshift-4.21" instead.

Details

In response to this:

Version(s):
4.21+

Issue:
OSDOCS-17764 / OSDOCS-15747

Link to docs preview:
Creating Spot VMs by using compute machine sets

QE review:

  • QE has approved this change.

Additional information:
⭐ Merge reviewers: second commit is for SME awareness, will squash before merging

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 openshift-eng/jira-lifecycle-plugin repository.

@ShaunaDiaz ShaunaDiaz added merge-review-in-progress Signifies that the merge review team is reviewing this PR and removed merge-review-needed Signifies that the merge review team needs to review this PR labels Jan 28, 2026
@miyadav
Copy link
Member

miyadav commented Jan 28, 2026

LGTM

Copy link
Contributor

@ShaunaDiaz ShaunaDiaz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@ShaunaDiaz ShaunaDiaz added ok-to-merge and removed merge-review-in-progress Signifies that the merge review team is reviewing this PR labels Jan 28, 2026
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 28, 2026
@jeana-redhat jeana-redhat force-pushed the OSDOCS-15747-gcp-spot-vm-mapi branch from 0c600ad to 61c6530 Compare January 28, 2026 19:06
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Jan 28, 2026
@openshift-ci
Copy link

openshift-ci bot commented Jan 28, 2026

New changes are detected. LGTM label has been removed.

@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 28, 2026

@jeana-redhat: This pull request references OSDOCS-15747 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the epic to target either version "4.22." or "openshift-4.22.", but it targets "openshift-4.21" instead.

Details

In response to this:

Version(s):
4.21+

Issue:
OSDOCS-17764 / OSDOCS-15747

Link to docs preview:
Creating Spot VMs by using compute machine sets

QE review:

  • QE has approved this change.

Additional information:
⭐ Merge reviewers: second commit is for SME awareness, will squash before merging

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 openshift-eng/jira-lifecycle-plugin repository.

@RadekManak
Copy link

lgtm

@jeana-redhat jeana-redhat force-pushed the OSDOCS-15747-gcp-spot-vm-mapi branch from 61c6530 to 762a542 Compare January 29, 2026 15:25
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 29, 2026

@jeana-redhat: This pull request references OSDOCS-15747 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the epic to target either version "4.22." or "openshift-4.22.", but it targets "openshift-4.21" instead.

Details

In response to this:

Version(s):
4.21+

Issue:
OSDOCS-17764 / OSDOCS-15747

Link to docs preview:
Creating Spot VMs by using compute machine sets

QE review:

  • QE has approved this change.

Additional information:

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci
Copy link

openshift-ci bot commented Jan 29, 2026

@jeana-redhat: all tests passed!

Full PR test history. Your PR dashboard.

Details

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. I understand the commands that are listed here.

@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 29, 2026

@jeana-redhat: This pull request references OSDOCS-15747 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the epic to target either version "4.22." or "openshift-4.22.", but it targets "openshift-4.21" instead.

Details

In response to this:

Version(s):
4.21+

Issue:
OSDOCS-17764 / OSDOCS-15747

Link to docs preview:
Creating Spot VMs by using compute machine sets

QE review:

  • QE has approved this change.

Additional information:

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 openshift-eng/jira-lifecycle-plugin repository.

@jeana-redhat jeana-redhat merged commit 0ce6b0d into openshift:main Jan 29, 2026
2 checks passed
@jeana-redhat
Copy link
Contributor Author

/cherrypick enterprise-4.21

@openshift-cherrypick-robot

@jeana-redhat: new pull request created: #105679

Details

In response to this:

/cherrypick enterprise-4.21

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

branch/enterprise-4.21 jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. ok-to-merge size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants