Kueueviz: Helm values.yaml for ingress annotations, tls and environment variables #6682

Smuger · 2025-08-27T20:36:13Z

What type of PR is this?

/kind feature

What this PR does / why we need it:

KueueViz frontend and backend Ingresses previously had hardcoded NGINX annotations.
- This PR allows you to set your own annotations in Helm's values.yaml, with NGINX as the default. You can for example disable nginx.ingress.kubernetes.io/ssl-redirect: "true"
KueueViz frontend and backend Ingresses also previously had hardcoded TLS.
- This PR allows you to use HTTP, which can be important for users who terminate TLS on AWS ALB.
The KueueViz backend deployment didn't expose environment variables.
- This PR allows you to set, for example, KUEUEVIZ_ALLOWED_ORIGINS from values.yaml.

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

I'm setting KUEUEVIZ_ALLOWED_ORIGINS to "frontend.kueueviz.local" by default. Let me know if there is a better option.

Does this PR introduce a user-facing change?

KueueViz: Enhancing the following endpoint customizations and optimizations:
- The frontend and backend ingress no longer have hardcoded NGINX annotations. You can now set your own annotations in Helm’s values.yaml using kueueViz.backend.ingress.annotations and kueueViz.frontend.ingress.annotations
- The Ingress resources for KueueViz frontend and backend no longer require hardcoded TLS. You can now choose to use HTTP only by not providing kueueViz.backend.ingress.tlsSecretName and kueueViz.frontend.ingress.tlsSecretName
- You can set environment variables like KUEUEVIZ_ALLOWED_ORIGINS directly from values.yaml using kueueViz.backend.env

netlify · 2025-08-27T20:36:20Z

✅ Deploy Preview for kubernetes-sigs-kueue canceled.

Name	Link
🔨 Latest commit	`121624f`
🔍 Latest deploy log	https://app.netlify.com/projects/kubernetes-sigs-kueue/deploys/68cc343ec6f6970008d3c6e2

linux-foundation-easycla · 2025-08-27T20:36:21Z

The committers listed above are authorized under a signed CLA.

✅ login: Smuger / name: Krzysztof Kwietniewski (121624f)

k8s-ci-robot · 2025-08-27T20:36:23Z

Welcome @Smuger!

It looks like this is your first PR to kubernetes-sigs/kueue 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/kueue has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

k8s-ci-robot · 2025-08-27T20:36:24Z

Hi @Smuger. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

mbobrovskyi · 2025-08-28T12:08:09Z

/ok-to-test

Smuger · 2025-09-01T11:22:19Z

/retest

Smuger · 2025-09-01T12:12:55Z

@mbobrovskyi
Thanks for approving the tests. It's all green now 🎉

Smuger · 2025-09-04T18:59:55Z

/area dashboard

mimowo · 2025-09-12T17:58:22Z

@mbobrovskyi
could you give it a pass? Seems like a useful feature

mbobrovskyi · 2025-09-15T07:39:07Z

config/components/kueueviz/backend-ingress.yaml

-  annotations:
-    nginx.ingress.kubernetes.io/rewrite-target: /
-    nginx.ingress.kubernetes.io/ssl-redirect: "true"


I understand that Helm charts aren't needed, but can we create a patch to retain it in the manifests?

Alternatively, revert the config changes and just update the annotations in the charts.

@mbobrovskyi
Sorry, I'm not sure if I understand. nginx annotations are still the default in values.yaml. Are you suggesting keeping the hardcoded nginx annotations in config and then overwriting them from values.yaml? I'm a bit worried about the added complexity

Yes, you configured the default value for the Helm charts — that’s good. But what about the Kustomize manifests? Many users install Kueue using manifests instead of Helm.

You can check the difference between manifests using make artifacts.

@mbobrovskyi
Thanks, I get it now. Kustomize patch added

mbobrovskyi · 2025-09-15T07:40:21Z

charts/kueue/tests/kueue_test.yaml

+          env: []
+    asserts:
+      - notExists:
+          path: spec.template.spec.containers[0].env[0]


nit: please add empty line at the end of this file.

@mbobrovskyi
Added empty line

mbobrovskyi · 2025-09-15T07:44:03Z

charts/kueue/values.yaml

+    # -- Environment variables for KueueViz backend deployment
+    env:
+      - name: KUEUEVIZ_ALLOWED_ORIGINS
+        value: "frontend.kueueviz.local"


Should we add the same for frontend?

@mbobrovskyi
Added environment variables for frontend

Smuger · 2025-09-15T14:26:28Z

/test all

k8s-ci-robot · 2025-09-15T14:44:20Z

@Smuger: The following commands are available to trigger required jobs:

/test pull-kueue-build-image-main

/test pull-kueue-test-e2e-certmanager-main

/test pull-kueue-test-e2e-customconfigs-main

/test pull-kueue-test-e2e-kueueviz-main

/test pull-kueue-test-e2e-main-1-31

/test pull-kueue-test-e2e-main-1-32

/test pull-kueue-test-e2e-main-1-33

/test pull-kueue-test-e2e-main-1-34

/test pull-kueue-test-e2e-multikueue-main

/test pull-kueue-test-e2e-tas-main

/test pull-kueue-test-integration-baseline-main

/test pull-kueue-test-integration-extended-main

/test pull-kueue-test-integration-multikueue-main

/test pull-kueue-test-scheduling-perf-main

/test pull-kueue-test-unit-main

/test pull-kueue-verify-main

Use /test all to run all jobs.

In response to this:

/test ?

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.

mbobrovskyi · 2025-09-16T12:12:59Z

config/kueueviz/kustomization.yaml

+
+patches:
+# Add ingress annotations for nginx backend ingress controller
+- path: backend_ingress_annotations_patch.yaml


What about frontend ingress?

added patch for frontend ingress

mbobrovskyi · 2025-09-16T12:13:19Z

config/kueueviz/frontend_deployment_env_patch.yaml

+        - name: frontend
+          env:
+            - name: REACT_APP_WEBSOCKET_URL
+              value: 'wss://backend.kueueviz.local'


nit: new line

new line added

mbobrovskyi · 2025-09-16T12:13:58Z

config/kueueviz/kustomization.yaml

+# Add ingress annotations for nginx backend ingress controller
+- path: backend_ingress_annotations_patch.yaml
+# Add environment variables for frontend deployment
+- path: frontend_deployment_env_patch.yaml


What about tls changes?

added tls patch

mimowo · 2025-09-18T13:00:25Z

/approve
/cherrypick release-0.13
/cherrypick release-0.12
Leaving lgtm to @mbobrovskyi

k8s-infra-cherrypick-robot · 2025-09-18T13:00:28Z

@mimowo: once the present PR merges, I will cherry-pick it on top of release-0.12, release-0.13 in new PRs and assign them to you.

In response to this:

/approve
/cherrypick release-0.13
/cherrypick release-0.12
Leaving lgtm to @mbobrovskyi

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.

k8s-ci-robot · 2025-09-18T13:00:34Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mimowo, Smuger

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~~ [mimowo]

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

mbobrovskyi · 2025-09-18T13:25:21Z

charts/kueue/values.yaml

    imagePullSecrets: []
    # -- Enable PriorityClass for KueueViz dashboard backend deployments
    priorityClassName:
+    # -- Environment variables for KueueViz backend deployment


Suggested change

# -- Environment variables for KueueViz backend deployment

# -- Environment variables for KueueViz frontend deployment

I'm guessing you mean the error here env frontend
Sorry for such a silly miss. Fixed

mbobrovskyi · 2025-09-18T13:26:51Z

charts/kueue/README.md

 | enableVisibilityAPF | bool | `false` | Enable API Priority and Fairness configuration for the visibility API |
 | fullnameOverride | string | `""` | Override the resource name |
 | kubernetesClusterDomain | string | `"cluster.local"` | Kubernetes cluster's domain |
+| kueueViz.backend.env | list | `[{"name":"KUEUEVIZ_ALLOWED_ORIGINS","value":"frontend.kueueviz.local"}]` | Environment variables for KueueViz backend deployment |


Suggested change

| kueueViz.backend.env | list | `[{"name":"KUEUEVIZ_ALLOWED_ORIGINS","value":"frontend.kueueviz.local"}]` | Environment variables for KueueViz backend deployment |

| kueueViz.backend.env | list | `[{"name":"KUEUEVIZ_ALLOWED_ORIGINS","value":"frontend.kueueviz.local"}]` | Environment variables for KueueViz frontend deployment |

Suggested change

| kueueViz.backend.env | list | `[{"name":"KUEUEVIZ_ALLOWED_ORIGINS","value":"frontend.kueueviz.local"}]` | Environment variables for KueueViz backend deployment |

| kueueViz.backend.env | list | `[{"name":"KUEUEVIZ_ALLOWED_ORIGINS","value":"backend.kueueviz.local"}]` | Environment variables for KueueViz backend deployment |

It look like still not correct. Could you please take a look?

I might be completly wrong so do let me know if I'm misunderstanding this.

Isn't setting env variable of backend deployment KUEUEVIZ_ALLOWED_ORIGINS to "frontend.kueueviz.local" correct? I can set it back to '*' if you want

This makes sense to me, wdyt @mbobrovskyi ?

…ined in Helm values; Add environment variables via values.yaml in frontend and backend deployment; kustomize patch ingress annotations and frontend deployment environment variables

mbobrovskyi · 2025-09-22T07:08:57Z

/lgtm
Thank you!

k8s-ci-robot · 2025-09-22T07:09:05Z

LGTM label has been added.

Git tree hash: 5f867f5dae8c80a852d506270dc22ee38bde9661

k8s-infra-cherrypick-robot · 2025-09-22T07:38:59Z

@mimowo: new pull request created: #6934

In response to this:

/approve
/cherrypick release-0.13
/cherrypick release-0.12
Leaving lgtm to @mbobrovskyi

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.

k8s-infra-cherrypick-robot · 2025-09-22T07:39:35Z

@mimowo: #6682 failed to apply on top of branch "release-0.12":

Applying: Allow annotations for Kueueviz frontend and backend ingress to be defined in Helm values; Add environment variables via values.yaml in frontend and backend deployment; kustomize patch ingress annotations and frontend deployment environment variables
.git/rebase-apply/patch:190: trailing whitespace.
            annotations: 
.git/rebase-apply/patch:236: trailing whitespace.
            annotations: 
warning: 2 lines add whitespace errors.
Using index info to reconstruct a base tree...
M	charts/kueue/README.md
M	charts/kueue/templates/kueueviz/backend-deployment.yaml
M	charts/kueue/templates/kueueviz/backend-ingress.yaml
M	charts/kueue/templates/kueueviz/frontend-deployment.yaml
M	charts/kueue/templates/kueueviz/frontend-ingress.yaml
A	charts/kueue/tests/kueue_test.yaml
M	charts/kueue/values.yaml
M	config/components/kueueviz/frontend-deployment.yaml
M	hack/processing-plan.yaml
Falling back to patching base and 3-way merge...
Auto-merging hack/processing-plan.yaml
CONFLICT (content): Merge conflict in hack/processing-plan.yaml
Auto-merging config/components/kueueviz/frontend-deployment.yaml
CONFLICT (content): Merge conflict in config/components/kueueviz/frontend-deployment.yaml
Auto-merging charts/kueue/values.yaml
CONFLICT (content): Merge conflict in charts/kueue/values.yaml
CONFLICT (modify/delete): charts/kueue/tests/kueue_test.yaml deleted in HEAD and modified in Allow annotations for Kueueviz frontend and backend ingress to be defined in Helm values; Add environment variables via values.yaml in frontend and backend deployment; kustomize patch ingress annotations and frontend deployment environment variables. Version Allow annotations for Kueueviz frontend and backend ingress to be defined in Helm values; Add environment variables via values.yaml in frontend and backend deployment; kustomize patch ingress annotations and frontend deployment environment variables of charts/kueue/tests/kueue_test.yaml left in tree.
Auto-merging charts/kueue/templates/kueueviz/frontend-ingress.yaml
CONFLICT (content): Merge conflict in charts/kueue/templates/kueueviz/frontend-ingress.yaml
Auto-merging charts/kueue/templates/kueueviz/frontend-deployment.yaml
CONFLICT (content): Merge conflict in charts/kueue/templates/kueueviz/frontend-deployment.yaml
Auto-merging charts/kueue/templates/kueueviz/backend-ingress.yaml
CONFLICT (content): Merge conflict in charts/kueue/templates/kueueviz/backend-ingress.yaml
Auto-merging charts/kueue/templates/kueueviz/backend-deployment.yaml
Auto-merging charts/kueue/README.md
CONFLICT (content): Merge conflict in charts/kueue/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 0001 Allow annotations for Kueueviz frontend and backend ingress to be defined in Helm values; Add environment variables via values.yaml in frontend and backend deployment; kustomize patch ingress annotations and frontend deployment environment variables

In response to this:

/approve
/cherrypick release-0.13
/cherrypick release-0.12
Leaving lgtm to @mbobrovskyi

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.

mimowo · 2025-09-22T07:42:19Z

@Smuger we cherrypicked for 0.13 using the robot, but there are conflicts on 0.12. If you want to cherrypick there the PR needs to be prepared manually. Otherwise we can just skip CP to 0.12.

tenzen-y · 2025-09-22T13:38:27Z

charts/kueue/README.md

 | enableVisibilityAPF | bool | `false` | Enable API Priority and Fairness configuration for the visibility API |
 | fullnameOverride | string | `""` | Override the resource name |
 | kubernetesClusterDomain | string | `"cluster.local"` | Kubernetes cluster's domain |
+| kueueViz.backend.env | list | `[{"name":"KUEUEVIZ_ALLOWED_ORIGINS","value":"frontend.kueueviz.local"}]` | Environment variables for KueueViz backend deployment |


IIUC, this .local top level domain is a bit dangerous since .local is reserved by mDNS usage and some ecosystem rely on that like zeroConf.

I hope that no one deploys this default value to their production.

I would definitly like to avoid this. I was unsure how to handle KUEUEVIZ_ALLOWED_ORIGINS from the start.

Should I set KUEUEVIZ_ALLOWED_ORIGINS in values.yaml to "" and let middleware inform the user that they need to explicilty set it in production?

How was KUEUEVIZ_ALLOWED_ORIGINS set before this PR?

@tenzen-y can you clarify why this is dangerous? Do you mean (1.) someone could hack KueueViz if deployed this way, or that (2.) it wouldn't work for environments not using "local".

IIUC it may not work on some environements, and require manual change, but so would empty "" also not work. In that case it seems fair to leave it using "local" as a default. wdyt?

Assuming (2.) - no attack risk, just "doesn't work", I'm ok to either leave it empty or set as frontend.kueueviz.local

1Q: In my opinion we should handle CORS like this
Development:
Should be set to: KUEUEVIZ_ALLOWED_ORIGINS = "*" by default making every origin valid
Production:
Should be set to KUEUEVIZ_ALLOWED_ORIGINS = "" by default making no origin valid. Expecting user to setup
their own domain

I'm ok with that in a follow up.

2Q I'm also for removing .local domain.

I'm ok for that in a follow up too.

1A: Specifying a dedicated CORS domain should be better in the production env. If not, some security risks occur like CSRF and XSS.

Yes, so it is better not to use *. Actually * was used before this PR.

IIUC, the * CORS origin is used only when development mode. So, I think that it is not bigger problem.

2A: .local domain is a reserved name. So, if we use this domain here, sometimes the intranet will break based on their network settings.

Yes, but if this is the case admins will be able to change. If this works in most setups maybe no need to change the default. It does not seem to have any risk - it may just not work.

I meant the affection potentially could reach across their entire internal networks. So, I mentioned that "I hope ... this default value to their production."

1Q: In my opinion we should handle CORS like this
Development:
Should be set to: KUEUEVIZ_ALLOWED_ORIGINS = "*" by default making every origin valid
Production:
Should be set to KUEUEVIZ_ALLOWED_ORIGINS = "" by default making no origin valid. Expecting user to setup their own domain

2Q I'm also for removing .local domain.
Should we just use localhost by default and tell people to use port-forwarding? Kubernetes-Dashboard does that

https://github.com/kubernetes/dashboard/blob/1d1d9f436f5def9f6a3a4f33757eed5175c53649/charts/kubernetes-dashboard/values.yaml#L105

https://github.com/kubernetes/dashboard/blob/1d1d9f436f5def9f6a3a4f33757eed5175c53649/charts/kubernetes-dashboard/templates/networking/ingress.yaml#L69

@Saumya40-codes Thanks for summarizing that. Both look good to me.

IIUC, the * CORS origin is used only when development mode. So, I think that it is not bigger problem.

I think this "developer" more is actually what we were releasing in 0.13 by default TBH. So, I think this PR making it "frontend.kueueviz.local" is making this more strict anyway.

I meant the affection potentially could reach across their entire internal networks. So, I mentioned that "I hope ... this default value to their production."

Can you clarify what you mean by that?

Basically, I think KueueViz needs to work OOTB just by enableKueueViz, otherwise users will hit issues.

So IIUC "frontend.kueueviz.local" is very useful as default setting. Sure, we can educate users they recommend changing (I'm still don't understand why / how).

Similarly, we recommend users to use HA mode for Kueue, but at least it works OOTB, I think we need to make KueueViz also works OOTB.

If we want to make KueueViz OOTB, * could be used as a default parameter with development mode.
But, if we want to make KueueViz deployable to production, avoiding both * and .local would be better.

Both * and .local have the same risk "level", but the "directions" are different.
* indicates security risk, .local indicates network disruption risk.
We might consider the .localhost domain, but we're not sure if it works correctly.

To be clear, my comment is "hope" for production. So, I don't try to enforce any approach. Some solutions are safe, but others are inconvenient.

tenzen-y · 2025-09-30T13:31:11Z

/release-note-edit

KueueViz: Enhancing the following endpoint customizations and optimizations:
- The frontend and backend ingress no longer have hardcoded NGINX annotations. You can now set your own annotations in Helm’s values.yaml using kueueViz.backend.ingress.annotations and kueueViz.frontend.ingress.annotations
- The Ingress resources for KueueViz frontend and backend no longer require hardcoded TLS. You can now choose to use HTTP only by not providing kueueViz.backend.ingress.tlsSecretName and kueueViz.frontend.ingress.tlsSecretName
- You can set environment variables like KUEUEVIZ_ALLOWED_ORIGINS directly from values.yaml using kueueViz.backend.env

k8s-ci-robot added release-note Denotes a PR that will be considered when it comes time to generate release notes. kind/feature Categorizes issue or PR as related to a new feature. labels Aug 27, 2025

k8s-ci-robot requested review from kannon92 and mimowo August 27, 2025 20:36

k8s-ci-robot added cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Aug 27, 2025

k8s-ci-robot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. and removed cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. labels Aug 27, 2025

Smuger force-pushed the kueueviz-dynamic-annotations-and-tls branch from 0104c99 to f6bc463 Compare September 1, 2025 11:18

k8s-ci-robot added the area/dashboard Denotes a PR that is related to the built-in dashboard label Sep 4, 2025

Smuger mentioned this pull request Sep 6, 2025

Add configuration parameters to kueue-viz backend (listen-port, logs, verbosity, etc...) #3880

Open

3 tasks

mbobrovskyi reviewed Sep 15, 2025

View reviewed changes

Smuger force-pushed the kueueviz-dynamic-annotations-and-tls branch from 8d2dfdd to 0f6f140 Compare September 15, 2025 14:42

mbobrovskyi reviewed Sep 16, 2025

View reviewed changes

k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 18, 2025

mbobrovskyi reviewed Sep 18, 2025

View reviewed changes

Allow annotations for Kueueviz frontend and backend ingress to be def…

121624f

…ined in Helm values; Add environment variables via values.yaml in frontend and backend deployment; kustomize patch ingress annotations and frontend deployment environment variables

Smuger force-pushed the kueueviz-dynamic-annotations-and-tls branch from f1249b8 to 121624f Compare September 18, 2025 16:33

k8s-ci-robot assigned mbobrovskyi Sep 22, 2025

k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Sep 22, 2025

k8s-ci-robot merged commit dd9f505 into kubernetes-sigs:main Sep 22, 2025
23 checks passed

k8s-ci-robot added this to the v0.14 milestone Sep 22, 2025

k8s-infra-cherrypick-robot mentioned this pull request Sep 22, 2025

[release-0.13] Kueueviz: Helm values.yaml for ingress annotations, tls and environment variables #6934

Merged

tenzen-y reviewed Sep 22, 2025

View reviewed changes

Smuger mentioned this pull request Sep 22, 2025

resolve 0.12 merge conflicts for helm values.yaml annotations and env #6948

Open

mimowo mentioned this pull request Sep 30, 2025

Release v0.14.0 #6756

Closed

36 tasks

	# -- Environment variables for KueueViz backend deployment
	# -- Environment variables for KueueViz frontend deployment

	\| kueueViz.backend.env \| list \| `[{"name":"KUEUEVIZ_ALLOWED_ORIGINS","value":"frontend.kueueviz.local"}]` \| Environment variables for KueueViz backend deployment \|
	\| kueueViz.backend.env \| list \| `[{"name":"KUEUEVIZ_ALLOWED_ORIGINS","value":"frontend.kueueviz.local"}]` \| Environment variables for KueueViz frontend deployment \|

Kueueviz: Helm values.yaml for ingress annotations, tls and environment variables #6682

Kueueviz: Helm values.yaml for ingress annotations, tls and environment variables #6682

Uh oh!

Conversation

Smuger commented Aug 27, 2025 • edited by k8s-ci-robot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

What type of PR is this?

What this PR does / why we need it:

Which issue(s) this PR fixes:

Special notes for your reviewer:

Does this PR introduce a user-facing change?

Uh oh!

netlify bot commented Aug 27, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

✅ Deploy Preview for kubernetes-sigs-kueue canceled.

Uh oh!

linux-foundation-easycla bot commented Aug 27, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

k8s-ci-robot commented Aug 27, 2025

Uh oh!

k8s-ci-robot commented Aug 27, 2025

Uh oh!

mbobrovskyi commented Aug 28, 2025

Uh oh!

Smuger commented Sep 1, 2025

Uh oh!

Smuger commented Sep 1, 2025

Uh oh!

Smuger commented Sep 4, 2025

Uh oh!

mimowo commented Sep 12, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

mbobrovskyi Sep 15, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

mbobrovskyi Sep 15, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Smuger commented Sep 15, 2025

Uh oh!

k8s-ci-robot commented Sep 15, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

mimowo commented Sep 18, 2025

Uh oh!

k8s-infra-cherrypick-robot commented Sep 18, 2025

Uh oh!

k8s-ci-robot commented Sep 18, 2025

Uh oh!

Choose a reason for hiding this comment

Smuger commented Aug 27, 2025 •

edited by k8s-ci-robot

Loading

netlify bot commented Aug 27, 2025 •

edited

Loading

linux-foundation-easycla bot commented Aug 27, 2025 •

edited

Loading

mbobrovskyi Sep 15, 2025 •

edited

Loading

mbobrovskyi Sep 15, 2025 •

edited

Loading

mimowo commented Sep 22, 2025 •

edited

Loading