CORENET-6714: Adding netobserv namespace exception for prometheus endpoint auth - #31447
CORENET-6714: Adding netobserv namespace exception for prometheus endpoint auth#31447OlivierCazade wants to merge 1 commit into
Conversation
|
Pipeline controller notification For optional jobs, comment This repository is configured in: automatic mode |
|
@OlivierCazade: This pull request references CORENET-6714 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "5.0.0" version, but no target version was set. DetailsIn 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. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository YAML (base), Central YAML (inherited) Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
WalkthroughThe Prometheus authorization test now excludes the ChangesPrometheus authorization validation
Estimated code review effort: 1 (Trivial) | ~2 minutes Suggested reviewers: 🚥 Pre-merge checks | ✅ 15✅ Passed checks (15 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
@OlivierCazade, |
|
/testwith openshift/cluster-network-operator/master/e2e-aws-ovn-techpreview-serial openshift/cluster-network-operator/3087 |
|
@OlivierCazade, |
|
/testwith openshift/cluster-network-operator/master/e2e-gcp-ovn-techpreview openshift/cluster-network-operator#3087 |
|
/testwith openshift/cluster-network-operator/master/e2e-aws-ovn-techpreview-serial openshift/cluster-network-operator#3087 |
simonpasquier
left a comment
There was a problem hiding this comment.
As I commented on Slack, I'd prefer if we updated netobserv to have a proper TLS setup.
The requirements are defined in https://github.com/openshift/enhancements/blob/master/CONVENTIONS.md#metrics
|
@simonpasquier And I agree that this would be better with authentication, and to add it before going GA. But as stated in the requirements you linked, this is not an hard requirement for Network Observability :
Network Observability is not a core operator, only an optional one and we are asking here to not block the techpreview for it. |
|
Scheduling required tests: |
|
Based on the message https://redhat-internal.slack.com/archives/C01CQA76KMX/p1785350439143599?thread_ts=1784821612.732699&cid=C01CQA76KMX, I am willing to approve this. It is optional operator and Tech Preview. Given there are already other operators rolling with this exception active since 4.10 (pointing fingers at cluster image registry with their OCPBUGS-5878 Jira open in January 2023). I did not manage to find any authoritative resource saying auth is "MUST" and not "SHOULD" at this level and I don't want netobserv folks to be blocked on this unless necessary. I would propose lazy consensus till end of Friday 31/July. |
|
To clarify the monitoring team's position: we have no intent to block the exception if staff engineering is ok with it. |
|
@OlivierCazade, |
|
/testwith openshift/cluster-network-operator/master/e2e-aws-ovn-techpreview-serial openshift/cluster-network-operator#3087 |
|
@OlivierCazade, |
|
@OlivierCazade, |
|
/testwith openshift/cluster-network-operator/master/e2e-gcp-ovn-techpreview openshift/cluster-network-operator#3087 |
1 similar comment
|
/testwith openshift/cluster-network-operator/master/e2e-gcp-ovn-techpreview openshift/cluster-network-operator#3087 |
I'm on the staff engineering and I approve. |
|
/approve @stleerh @OlivierCazade please share when you're planning to fix the exception. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: OlivierCazade, simonpasquier The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/testwith openshift/cluster-network-operator/master/e2e-aws-ovn-techpreview-serial openshift/cluster-network-operator#3087 |
|
@simonpasquier I created the following task : I will be in on vacations the two next weeks, but this will by my main focus when I come back. |
|
/testwith openshift/cluster-network-operator/master/e2e-gcp-ovn-techpreview-serial-1of2 openshift/cluster-network-operator#3087 |
|
@OlivierCazade, |
|
/testwith openshift/cluster-network-operator/master/e2e-aws-ovn-single-node-techpreview openshift/cluster-network-operator#3087 |
|
@OlivierCazade, |
|
/testwith e2e-aws-ovn-single-node-techpreview openshift/cluster-network-operator#3087 |
|
@kapjain-rh, |
|
/testwith openshift/cluster-network-operator/master/e2e-aws-ovn-techpreview-serial openshift/cluster-network-operator#3087 |
|
@OlivierCazade: This PR was included in a payload test run from openshift/cluster-network-operator#3087
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/05ab5790-8d19-11f1-8621-201e42aa651a-0 |
|
@OlivierCazade: This PR was included in a payload test run from openshift/cluster-network-operator#3087
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/2705daf0-8d19-11f1-8775-0541fbb3da39-0 |
|
@OlivierCazade: This PR was included in a payload test run from openshift/cluster-network-operator#3087
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/2a781e50-8d19-11f1-9239-4816b026a852-0 |
|
@OlivierCazade: This PR was included in a payload test run from openshift/cluster-network-operator#3087
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/2d434c40-8d19-11f1-9973-5b6c8c40568f-0 |
|
/testwith openshift/cluster-network-operator/master/e2e-aws-ovn-techpreview-serial openshift/cluster-network-operator#3087 |
Network Observability operator is GA itself for some years now and is part of the RH catalog but is not part of the payload.
We have been working on enabling it by default. To do this we have agreed to have the CNO create the ClusterExtension object which will trigger an OLM install.
Having Network observability installed by default triggered a lot of tests and requirements linked to payload elements which Network Observability is not. (We still have to investigate some of them because we are not sure if this is appropriate to annotate the Network Observability component with payload associated annotations.)
For some of them not deploying to an openshift- cluster was enough to not trigger them, and we have aggreed to come back to them before going GA for this feature.
The last ones are linked to the metric endpoints of some of the components, for now this components have network policies and we support enabling TLS but we do not support authentication.
I am asking if we could add exception to this authentication rule while this feature is still in techpreview to no block the release of the techpreview of this feature.
Summary by CodeRabbit