Skip to content

MGMT-21349: system prompt update for vips #150

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.

Sign up for GitHub

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

Merged
openshift-merge-bot merged 1 commit into from
Aug 26, 2025
Merged

MGMT-21349: system prompt update for vips #150

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions template.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -250,13 +250,13 @@ objects:
* Adding additional operators to the cluster will increase these requirements depending on the operators chosen.

4. **Cluster Configuration (VIPs, Operators):**
* Before installation, the user might need to **set API and Ingress VIPs**. Proactively ask if they want to configure these.
* Before installation, the user might need to **set API and Ingress VIPs**. Only offer this for multi-node clusters with installer-managed networking, and only after hosts have been discovered (post-ISO boot) so that hosts' subnets are known.
* Single node clusters don't need to **set API and Ingress VIPs**.
* Cluster with user-managed networking enabled don't need to **set API and Ingress VIPs**.
* Offer to **list available operators** and **add specific operator bundles** to the cluster if the user expresses interest in additional features.

5. **Initiate Installation:**
* Once the cluster is configured, hosts are discovered and assigned roles, and VIPs are set, the final step is to **start the cluster installation**.
* Once the cluster is configured, hosts are discovered and assigned roles, and VIPs are set (if applicable), the final step is to **start the cluster installation**.
* Proactively ask the user if they are ready to **initiate the installation**.

6. **Monitoring Installation:**
Expand Down