telco-ran: OCPBUGS-63008: Improve RAN monitoring footprint CR to get alertmanager url from MCL annotation

[abraham2512]

This PR includes updates for merging RAN monitoring configuration with ACM observability.

• Hub side policy to be applied on observability namespace. Copies the route for alertmanager to the managedcluster CR annotation
• Updates ReduceMonitoringFootprint reference CR to use URL from the managedcluster annotations

[openshift-ci-robot]

@abraham2512: This pull request references Jira Issue OCPBUGS-63008, which is invalid:

• expected the bug to target the "4.21.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

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 openshift-eng/jira-lifecycle-plugin repository.

[abraham2512]

/retest

[openshift-ci-robot]

@abraham2512: This pull request references Jira Issue OCPBUGS-63008, which is invalid:

• expected the bug to target the "4.21.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

Updates regarding merging RAN monitoring configuration with ACM observability.

• Policy on the hub side to be applied on observability namespace to copy the route for alertmanager to the managedcluster CR annotations.
• Updates to the reference CRs to fetch the URL from the managedcluster annotations instead of fromSecret.

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 openshift-eng/jira-lifecycle-plugin repository.

[abraham2512]

/cherry-pick release-4.20

[openshift-cherrypick-robot]

@abraham2512: once the present PR merges, I will cherry-pick it on top of release-4.20 in a new PR and assign it to you.

In response to this:

/cherry-pick release-4.20

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.

[abraham2512]

/ @irinamihai @imiller0

[openshift-ci-robot]

@abraham2512: This pull request references Jira Issue OCPBUGS-63008, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.21.0) matches configured target version for branch (4.21.0)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @dgonyier

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

This PR includes updates for merging RAN monitoring configuration with ACM observability.

• Hub side policy to be applied on observability namespace. Copies the route for alertmanager to the managedcluster CR annotation
• Updates ReduceMonitoringFootprint reference CR to use URL from the managedcluster annotations

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 openshift-eng/jira-lifecycle-plugin repository.

[dgonyier]

@abraham2512 what is the intended setup and behavior if ACM observability is not enabled on the hub?

[abraham2512]

Hi @dgonyier. If ACM observability is not setup on the hub, this namespace open-cluster-management-addon-observability would not exist on the spoke. Therefore the lookup for alertmanager URL would not occur.
The policy would still remain compliant.

[irinamihai]

/retest

[irinamihai]

/lgtm
/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: abraham2512, irinamihai

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [irinamihai]

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

[openshift-ci-robot]

@abraham2512: Jira Issue OCPBUGS-63008: All pull requests linked via external trackers have merged:

• openshift-kni/telco-reference#406

Jira Issue OCPBUGS-63008 has been moved to the MODIFIED state.

In response to this:

This PR includes updates for merging RAN monitoring configuration with ACM observability.

• Hub side policy to be applied on observability namespace. Copies the route for alertmanager to the managedcluster CR annotation
• Updates ReduceMonitoringFootprint reference CR to use URL from the managedcluster annotations

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-cherrypick-robot]

@abraham2512: #406 failed to apply on top of branch "release-4.20":

Applying: telco-ran: obs-route-policy for annotating mcl with alertmanager url
Applying: add note
Applying: telco-hub: update readme
Applying: telco-ran: add note in kube-compare
Applying: telco-hub: update readme
Using index info to reconstruct a base tree...
M	telco-hub/configuration/reference-crs/required/acm/readme.md
Falling back to patching base and 3-way merge...
Auto-merging telco-hub/configuration/reference-crs/required/acm/readme.md
CONFLICT (content): Merge conflict in telco-hub/configuration/reference-crs/required/acm/readme.md
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0005 telco-hub: update readme

In response to this:

/cherry-pick release-4.20

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.