Skip to content

Conversation

Vincent056
Copy link
Contributor

Add a variable for excluded namespaces in the routes rate limit check

Introduce a new variable 'var_routes_excluded_namespaces_regex' to define namespaces that should be excluded from the routes rate limit compliance check.

@jan-cerny jan-cerny added the OpenShift OpenShift product related. label Oct 16, 2025
@Vincent056 Vincent056 changed the title CMP-3589: Add variable for excluded namespaces CMP-3589: Add variable for routes rate limit Oct 16, 2025
…heck

Introduce a new variable 'var_routes_excluded_namespaces_regex' to define namespaces that should be excluded from the routes rate limit compliance check.
Copy link

openshift-ci bot commented Oct 17, 2025

@Vincent056: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-aws-openshift-node-compliance cd3e7d4 link true /test e2e-aws-openshift-node-compliance

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

interactive: false

options:
default: "None"
Copy link
Collaborator

Choose a reason for hiding this comment

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

Should the default value here be kube and openshift to maintain backwards compatibility?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

that's a good catch, I am hard coding that to be part of the jq filter

An example allowing additional namespaces follows:
<pre>
apiVersion: compliance.openshift.io/v1alpha1
kind: TailoredProfile
Copy link
Collaborator

Choose a reason for hiding this comment

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

We don't typically put references like this in the rule descriptions. A reference to the documentation might be fine. Also, users consuming these through ACS might have a disjointed experience unless they can access the clusters this applies to.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

That's a good point!

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

Labels

OpenShift OpenShift product related.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants