Skip to content

Conversation

@arya-girish-k
Copy link
Contributor

@arya-girish-k arya-girish-k commented Aug 12, 2025

Description

https://github.ibm.com/GoldenEye/issues/issues/15542

  • Add the keyword "ROKS" to OCP DA
  • In diagram KMS -> Key Protect
  • Updated description for dependant DA.

Release required?

  • No release
  • Patch release (x.x.X)
  • Minor release (x.X.x)
  • Major release (X.x.x)
Release notes content

Run the pipeline

If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.

Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:

/run pipeline

Checklist for reviewers

  • If relevant, a test for the change is included or updated with this PR.
  • If relevant, documentation for the change is included or updated with this PR.

For mergers

  • Use a conventional commit message to set the release level. Follow the guidelines.
  • Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
  • Use the Squash and merge option.

@arya-girish-k arya-girish-k changed the title fix: Address ROKS DA E2E walkthrough feedback [WIP]fix: Address ROKS DA E2E walkthrough feedback Aug 12, 2025
@arya-girish-k
Copy link
Contributor Author

/run pipeline

@arya-girish-k arya-girish-k marked this pull request as ready for review August 12, 2025 13:05
@arya-girish-k
Copy link
Contributor Author

/run pipeline

@arya-girish-k arya-girish-k changed the title [WIP]fix: Address ROKS DA E2E walkthrough feedback chore: Address ROKS DA E2E walkthrough feedback Aug 13, 2025
Copy link
Contributor

@ocofaigh ocofaigh left a comment

Choose a reason for hiding this comment

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

You cant just go updating the versions of all of the DA add-ons - it will break something. The same DA versions needs to be used across all of the dependant DAs that are defined. We are in the process of rolling out updates to all dependant DA - Vipin will eventually be updating this DA. Please remove the changes you made to updating DA versions - I'm not sure why this was done in this PR?

I also noticed that the diagram says "Key for registry bucket" - this is NOT true. The registry bucket cant even be encrypted (we don't create it in this DA). The Key Protect key is used for encrypting the cluster and the boot volumes used by the cluster

arya-girish-k and others added 4 commits August 18, 2025 22:10
Co-authored-by: Shikha Maheshwari <[email protected]>
Co-authored-by: Shikha Maheshwari <[email protected]>
Co-authored-by: Shikha Maheshwari <[email protected]>
@arya-girish-k
Copy link
Contributor Author

/run pipeline

ibm_catalog.json Outdated
{
"name": "deploy-arch-ibm-kms",
"description": "Enable Cloud Automation for Key Protect when you want services to use your own managed encryption keys. If disabled, it will fall back on IBM Cloud's default service-managed encryption. ",
"description": "Configure Key Protect to use your own managed encryption keys for Object Storage bucket.",
Copy link
Contributor

Choose a reason for hiding this comment

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

Configures Key Protect to manage and use encryption keys for COS bucket.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Updated architecture description for fully configurable DA as well.

ibm_catalog.json Outdated
"type": "image/svg+xml"
},
"description": "This QuickStart variation of deployable architecture enables deployment of a <b>Red Hat OpenShift cluster</b> within an IBM Cloud Virtual Private Cloud (VPC). It provisions the OpenShift cluster and its foundational VPC infrastructure with a limited set of essential options for rapid and streamlined setup. Additionally, the deployment creates an <b>Object Storage bucket</b> that serves as the internal container image registry for the OpenShift cluster. Thus, it helps ensure seamless storage integration.<br><br>Users can select from predefined cluster sizes — <b>mini (default), small, medium, and large.</b> Each size determining the number of availability zones, worker nodes per zone, and the <b>machine type</b> (worker node flavor). [Learn more](https://github.com/terraform-ibm-modules/terraform-ibm-base-ocp-vpc/blob/main/solutions/quickstart/DA_docs.md).<br><br>By default, the architecture provisions a <b>two-zone VPC</b>, forming the foundation for the OpenShift cluster. The cluster comprises a single worker pool distributed across these zones, with <b>two worker nodes per zone</b> in the mini configuration.<br><br>This streamlined architecture balances ease of use with flexibility, enabling rapid OpenShift cluster deployments with the infrastructure, integrated storage services, and right-sized compute resources of IBM Cloud."
"description": "This QuickStart variation of deployable architecture enables deployment of a <b>Red Hat OpenShift cluster</b> within an IBM Cloud Virtual Private Cloud (VPC). It provisions the OpenShift cluster and its foundational VPC infrastructure with a limited set of essential options for rapid and streamlined setup. Additionally, the deployment creates an <b>Object Storage bucket</b> that serves as the internal container image registry for the OpenShift cluster. Thus, it helps ensure seamless storage integration.<br><br>Users can select from predefined cluster sizes — <b>mini (default), small, medium, and large.</b> Each size determines the number of availability zones, worker nodes per zone, and the <b>machine type</b> (worker node flavor). [Learn more](https://github.com/terraform-ibm-modules/terraform-ibm-base-ocp-vpc/blob/main/solutions/quickstart/DA_docs.md).<br><br>By default, the architecture provisions a <b>two-zone VPC</b>, forming the foundation for the OpenShift cluster. The cluster comprises a single worker pool distributed across these zones, with <b>two worker nodes per zone</b> in the mini configuration.<br><br>This streamlined architecture balances ease of use with flexibility, enabling rapid OpenShift cluster deployments with the infrastructure, integrated storage services, and right-sized compute resources of IBM Cloud."
Copy link
Contributor

Choose a reason for hiding this comment

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

This QuickStart FSCloud variation of deployable architecture enables deployment of a Red Hat OpenShift cluster within an IBM Cloud Virtual Private Cloud (VPC). It provisions the OpenShift cluster and its foundational VPC infrastructure with a limited set of essential options for rapid and streamlined setup. Additionally, the deployment creates an Object Storage bucket that serves as the internal container image registry for the OpenShift cluster. Thus, it helps ensure seamless storage integration.

Users can select from predefined cluster sizes — mini (default), small, medium, and large. Each size determines the number of availability zones, worker nodes per zone, and the machine type (worker node flavor). Learn more.

By default, the architecture provisions a two-zone VPC, forming the foundation for the OpenShift cluster. The cluster comprises a single worker pool distributed across these zones, with two worker nodes per zone in the mini configuration.

This streamlined architecture balances ease of use with flexibility, enabling rapid OpenShift cluster deployments with the infrastructure, integrated storage services, and right-sized compute resources of IBM Cloud.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Quickstart is the variation name used in this module, so the description will remain unchanged.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

arya-girish-k and others added 6 commits August 20, 2025 15:10
Co-authored-by: Shikha Maheshwari <[email protected]>
Co-authored-by: Shikha Maheshwari <[email protected]>
Co-authored-by: Shikha Maheshwari <[email protected]>
Co-authored-by: Shikha Maheshwari <[email protected]>
Co-authored-by: Shikha Maheshwari <[email protected]>
Copy link
Member

@maheshwarishikha maheshwarishikha left a comment

Choose a reason for hiding this comment

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

Service official name is Event Notifications - please use the same in diagram.

arya-girish-k and others added 4 commits August 21, 2025 10:51
Co-authored-by: Shikha Maheshwari <[email protected]>
Co-authored-by: Shikha Maheshwari <[email protected]>
Co-authored-by: Shikha Maheshwari <[email protected]>
@arya-girish-k
Copy link
Contributor Author

Service official name is Event Notifications - please use the same in diagram.

Updated in the diagram

@arya-girish-k
Copy link
Contributor Author

/run pipeline

@arya-girish-k
Copy link
Contributor Author

/run pipeline

Copy link
Member

@maheshwarishikha maheshwarishikha left a comment

Choose a reason for hiding this comment

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

LGTM

@maheshwarishikha maheshwarishikha dismissed stale reviews from vburckhardt and ocofaigh August 21, 2025 08:46

Feedback addressed

@maheshwarishikha maheshwarishikha merged commit 39d65ba into main Aug 21, 2025
2 checks passed
@maheshwarishikha maheshwarishikha deleted the issue-15542 branch August 21, 2025 08:56
@terraform-ibm-modules-ops
Copy link
Contributor

🎉 This PR is included in version 3.55.4 🎉

The release is available on:

Your semantic-release bot 📦🚀

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants