Skip to content

proxy-aae: override WORKERS_SECRET_NAMESPACE for OpenShift#3244

Merged
tekton-robot merged 1 commit intotektoncd:mainfrom
khrm:proxy-aae-openshift-namespace-transform
Feb 27, 2026
Merged

proxy-aae: override WORKERS_SECRET_NAMESPACE for OpenShift#3244
tekton-robot merged 1 commit intotektoncd:mainfrom
khrm:proxy-aae-openshift-namespace-transform

Conversation

@khrm
Copy link
Contributor

@khrm khrm commented Feb 24, 2026

On OpenShift, the kueue operator runs in the openshift-kueue-operator namespace rather than the upstream default kueue-system. Add an OpenShift transform in the proxy-aae extension to replace the WORKERS_SECRET_NAMESPACE env var accordingly. Export DeploymentEnvVars in the common package to make the transformer reusable. Add tests covering both the default transform and the ability for spec.options to override the value.

Changes

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you
review them:

See the contribution guide for more details.

Release Notes

NONE

@tekton-robot tekton-robot added the release-note-none Denotes a PR that doesnt merit a release note. label Feb 24, 2026
@tekton-robot tekton-robot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Feb 24, 2026
Copy link
Contributor Author

@khrm khrm left a comment

Choose a reason for hiding this comment

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

@khrm
Copy link
Contributor Author

khrm commented Feb 24, 2026

/kind bug

@tekton-robot tekton-robot added the kind/bug Categorizes issue or PR as related to a bug. label Feb 24, 2026
common.DeploymentEnvVars([]corev1.EnvVar{
{
Name: "WORKERS_SECRET_NAMESPACE",
Value: "openshift-kueue-operator",
Copy link
Member

Choose a reason for hiding this comment

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

instead of hardcoding the namespace. can we extract this from some kueue resource ?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Isn't the worker secret needed in Kueue's namespace? That's why we need to configure it.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

If it's installed somewhere, we can use options.

Copy link
Member

Choose a reason for hiding this comment

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

There is always an option to install the kueue operator in non-default namespace.
SO if customer installs there. then this will fail

image

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Customer can set options field on deployment to change this environment variable.

Copy link
Member

Choose a reason for hiding this comment

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

editing operator owned deployment is not something they should be doing. Maybe we can set this value in tektonconfig if namespace is different from default

So in scheduler config. can we have a field called kueue-namespace which defaults to "openshift-kueue-operator" in openshift and kueue-system in kubernetes

Copy link
Contributor Author

Choose a reason for hiding this comment

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

No, they aren't editing deployment. They are using the options field. Check the document.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@khrm khrm force-pushed the proxy-aae-openshift-namespace-transform branch 2 times, most recently from 7b1828a to 2f55233 Compare February 25, 2026 13:00
On OpenShift, the kueue operator runs in the openshift-kueue-operator
namespace rather than the upstream default kueue-system. Add an OpenShift
transform in the proxy-aae extension to replace the WORKERS_SECRET_NAMESPACE
env var accordingly. Export DeploymentEnvVars in the common package to make
the transformer reusable. Add tests covering both the default transform and
the ability for spec.options to override the value.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@khrm khrm force-pushed the proxy-aae-openshift-namespace-transform branch from 2f55233 to b7561bc Compare February 26, 2026 11:11
@pramodbindal
Copy link
Member

/lgtm

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Feb 27, 2026
@jkhelil
Copy link
Member

jkhelil commented Feb 27, 2026

/approve

@tekton-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jkhelil

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

The pull request process is described here

Details Needs approval from an approver in each of these files:

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

@tekton-robot tekton-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 27, 2026
@tekton-robot tekton-robot merged commit 4f60bb9 into tektoncd:main Feb 27, 2026
14 checks passed
@khrm khrm deleted the proxy-aae-openshift-namespace-transform branch February 27, 2026 09:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. kind/bug Categorizes issue or PR as related to a bug. lgtm Indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesnt merit a release note. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants