Skip to content

Conversation

sraviteja-maker
Copy link
Contributor

@sraviteja-maker sraviteja-maker commented Sep 3, 2025

This functionality will help us to scale out the existing SNO Cluster where we can create clusters with SNO+1,SNO+2...SNO+N Deployment models for our internal testing.

It will be very useful for getting around the lab resource constraints.

Copy link

openshift-ci bot commented Sep 3, 2025

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

Copy link

openshift-ci bot commented Sep 3, 2025

[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 rsevilla87 for approval. For more information see the 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:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@sraviteja-maker sraviteja-maker marked this pull request as ready for review September 3, 2025 11:35
@sraviteja-maker
Copy link
Contributor Author

sraviteja-maker commented Sep 3, 2025

Please find the logs for your reference for successful scale out in SNO Cluster

sno-scale-out-testing-1756719528.log

image

@rsevilla87
Copy link
Member

/cc @akrzos

@openshift-ci openshift-ci bot requested a review from akrzos September 3, 2025 13:16

## Add Nodes to Worker Inventory

You can add new entries to the worker inventory section manually. Place them at the end of the list of worker entries.
Copy link
Member

Choose a reason for hiding this comment

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

Can we use the create-inventory playbook to generate the worker entries? Since they have values that could be tedious to copy manually.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Good Idea...Let me look into it.

Copy link
Member

@afcollins afcollins left a comment

Choose a reason for hiding this comment

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

Thank you! Looking good. Left some comments..

@sraviteja-maker
Copy link
Contributor Author

/test ?

Copy link

openshift-ci bot commented Sep 9, 2025

@sraviteja-maker: The following commands are available to trigger required jobs:

/test deploy-compact
/test deploy-mno
/test deploy-mno-hybrid
/test deploy-mno-scaleout
/test deploy-sno
/test deploy-sno-private-vlan
/test deploy-sno-self-sched

In response to this:

/test ?

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.

@sraviteja-maker
Copy link
Contributor Author

/test deploy-mno-scaleout

@sraviteja-maker
Copy link
Contributor Author

/test deploy-sno

Copy link

openshift-ci bot commented Sep 9, 2025

@sraviteja-maker: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/deploy-sno 6a49a41 link true /test deploy-sno

Full PR test history. Your PR dashboard.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants