Skip to content

Conversation

@mukulpalit-ibm
Copy link
Contributor

@mukulpalit-ibm mukulpalit-ibm commented Dec 1, 2025

Description

The PR adds a new module for monolith. This module integrates essential foundational services for security, monitoring, and logging for creating a fully configurable OCP cluster on an IBM Cloud Virtual Private Cloud. The example is added to other_tests.go

Test passed in schematics
Screenshot 2025-12-03 at 2 57 45 AM
Screenshot 2025-12-03 at 2 58 30 AM

Release required?

Adding a plain monolith example of base-ocp-vpc DA deployment by creating the add ons using terraform code.

  • 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.

@mukulpalit-ibm
Copy link
Contributor Author

/run pipeline

1 similar comment
@mukulpalit-ibm
Copy link
Contributor Author

/run pipeline

@mukulpalit-ibm
Copy link
Contributor Author

/run pipeline

1 similar comment
@mukulpalit-ibm
Copy link
Contributor Author

/run pipeline

@mukulpalit-ibm
Copy link
Contributor Author

/run pipeline

@mukulpalit-ibm
Copy link
Contributor Author

/run pipeline

@mukulpalit-ibm
Copy link
Contributor Author

/run pipeline

@mukulpalit-ibm
Copy link
Contributor Author

/run pipeline

cos_instance_guid = var.existing_cos_instance_crn != null ? module.existing_cos_instance_crn_parser[0].service_instance : module.cos[0].cos_instance_guid
}

module "cloud_logs" {
Copy link
Contributor

Choose a reason for hiding this comment

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

In addons flow, we were having dependencies on just observability instances and couldn't add dependency on observability agents because agents would be installed after cluster creation and addons flow wouldn't work for agents in that case. As now we are having a monolith example, we can call logs-agent module also. Currently we are just creating cloud logs instance but it is not used until logs-agent is installed. I suggest to include logs-agent module also.

Copy link
Contributor

@vkuma17 vkuma17 left a comment

Choose a reason for hiding this comment

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

looks good overall, just have some suggestions related to observability

}] : []
}

module "cloud_monitoring" {
Copy link
Contributor

Choose a reason for hiding this comment

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

In addons flow, we were having dependencies on just observability instances and couldn't add dependency on observability agents because agents would be installed after cluster creation and addons flow wouldn't work for agents in that case. As now we are having a monolith example, we can call monitoring-agent module also. Currently we are just creating cloud monitoring instance but it is not used until monitoring-agent is installed. I suggest to include monitoring-agent module also.

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