You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
For uds-core policy exemptions, there might be a case for optionally locking down which namespace the operator watches for Exemption CRs. With the current implementation of .InNamespace(), it does not look to be possible to set it to a single namespace or list / all namespaces based on env var. (e.g. .InNamespace(process.env.EXEMPTION_NS))
Describe the solution you'd like
Given an admin wants the option to allow single or all namespaces in .InNamespace(), or maybe namespaces that fit a pattern
he or she could use a regex patterns like so .InNamspace(".*") , .InNamespace("uds-policy-exemptions"), .InNamespace("*-policy-exemptions")
Describe alternatives you've considered
The alternative is to do this as the module author in the validator and not use .InNamespace().
The text was updated successfully, but these errors were encountered:
I think we could add something for this, but it wouldn't work really for watch as that modifies a URL to the API server. We also support multiple (array) of namespaces.
Is your feature request related to a problem? Please describe.
For uds-core policy exemptions, there might be a case for optionally locking down which namespace the operator watches for Exemption CRs. With the current implementation of
.InNamespace()
, it does not look to be possible to set it to a single namespace or list / all namespaces based on env var. (e.g..InNamespace(process.env.EXEMPTION_NS)
)Describe the solution you'd like
.InNamespace()
, or maybe namespaces that fit a pattern.InNamspace(".*")
,.InNamespace("uds-policy-exemptions")
,.InNamespace("*-policy-exemptions")
Describe alternatives you've considered
The alternative is to do this as the module author in the validator and not use
.InNamespace()
.The text was updated successfully, but these errors were encountered: