Expose CheckClusterIngressHealthy to the pr_test.go

[dishankkalra23]

Description

This PR exposes CheckClusterIngressHealthy to the pr_test.go to know the ingress state of the cluster.

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

Release required?

• No release
• Patch release (x.x.X)
• Minor release (x.X.x)
• Major release (X.x.x)

Release notes content

Addition of getClusterIngress method to expose the ingress state of the cluster

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.

[dishankkalra23]

/run pipeline

[dishankkalra23]

TestRunRoksPattern is getting skipped and PostApplyHook doesn't initiate

[dishankkalra23]

@ocofaigh @toddgiguere The PostApplyHook never executes because TestRunRoksPattern are skipped when enableSchematicsTests is True. Where should we add the hook because other test methods like TestRunVSIPattern, TestRunVpcPattern are also getting skipped.

[dishankkalra23]

The landing zone tests executes in schematics and post apply hook is yet to be supported in schematics.

[dishankkalra23]

Taking this to deep dive today to decide whether we add a support for post apply hook in schematics or is there any other way to approach it?

[dishankkalra23]

I ran TestRunRoksPattern in local after commenting out enableSchematicsTests and I found that this example creates more than one cluster.

TestRunRoksPattern 2024-09-16T13:54:54+05:30 logger.go:66:   "cluster_names": {
TestRunRoksPattern 2024-09-16T13:54:54+05:30 logger.go:66:     "sensitive": false,
TestRunRoksPattern 2024-09-16T13:54:54+05:30 logger.go:66:     "type": [
TestRunRoksPattern 2024-09-16T13:54:54+05:30 logger.go:66:       "tuple",
TestRunRoksPattern 2024-09-16T13:54:54+05:30 logger.go:66:       [
TestRunRoksPattern 2024-09-16T13:54:54+05:30 logger.go:66:         "string",
TestRunRoksPattern 2024-09-16T13:54:54+05:30 logger.go:66:         "string"
TestRunRoksPattern 2024-09-16T13:54:54+05:30 logger.go:66:       ]
TestRunRoksPattern 2024-09-16T13:54:54+05:30 logger.go:66:     ],
TestRunRoksPattern 2024-09-16T13:54:54+05:30 logger.go:66:     "value": [
TestRunRoksPattern 2024-09-16T13:54:54+05:30 logger.go:66:       "ocp-ioblal-management-cluster",
TestRunRoksPattern 2024-09-16T13:54:54+05:30 logger.go:66:       "ocp-ioblal-workload-cluster"
TestRunRoksPattern 2024-09-16T13:54:54+05:30 logger.go:66:     ]
TestRunRoksPattern 2024-09-16T13:54:54+05:30 logger.go:66:   },

[dishankkalra23]

This module utilizes schematics to run the tests and support for post apply hook is not supported in schematics. I will create an issue to track the addition of support of post apply hook in schematics, after which CheckClusterIngressHealthy can be exposed in the landing zone

[dishankkalra23]

Closing this PR as postapply hook feature is yet to be supported in schematics workspace. I will be creating an issue to support postapply hook in schematics post which support for CheckClusterIngressHealthy can be added.

[dishankkalra23]

Issue to support postapply hook in schematics: https://github.ibm.com/GoldenEye/issues/issues/11065