Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

gatewayProxies deployment's .kind.deployment.priorityClassName is not implemented #9010

Closed
zelig81 opened this issue Dec 21, 2023 · 2 comments
Assignees

Comments

@zelig81
Copy link

zelig81 commented Dec 21, 2023

Gloo Edge Product

Open Source

Gloo Edge Version

1.14.21

Kubernetes Version

v1.26.8

Describe the bug

when I set priorityClassName in values of helm chart for gatewayProxy (in gatewayProxies.NAME.kind.deployment.priorityClassName) it is not set on the resulting NAME deployment. The proxies are created though.

example of values:

...
gatewayProxies:
  gatewayProxy:
    kind:
      deployment:
        priorityClassName: cluster-critical-priority-preempting
...
  internalProxy:
    kind:
      deployment:
        priorityClassName: cluster-critical-priority-preempting
...

Expected Behavior

resulting deployments for gateway-proxy and internal-proxy should contain priorityClassName

Steps to reproduce the bug

helm install ...

Additional Environment Detail

No response

Additional Context

after having a look on gateway proxy template, I see that .kind.deployment is in use only for configuration of replicas, customEnv and affinity specifically. Could you please add the absent values per documentation for gatewayProxies.NAME.kind.deployment.XXXXXX to be set in the resulting deployments?

(most important for me are nodeSelector and priorityClassName)

As possible solution - kubeResourceOverride can be used (to be merged with deployment spec), but after multiple tries I did not find any working formula with this key :sad

┆Issue is synchronized with this Asana task by Unito

@zelig81 zelig81 added the Type: Bug Something isn't working label Dec 21, 2023
Copy link

This issue has been marked as stale because of no activity in the last 180 days. It will be closed in the next 180 days unless it is tagged "no stalebot" or other activity occurs.

@github-actions github-actions bot added the stale Issues that are stale. These will not be prioritized without further engagement on the issue. label Jun 23, 2024
@sam-heilbron sam-heilbron self-assigned this Aug 15, 2024
@github-actions github-actions bot removed the stale Issues that are stale. These will not be prioritized without further engagement on the issue. label Aug 16, 2024
@sam-heilbron
Copy link
Contributor

See #8025 (comment) for more context. This was resolved in GG Enterprise 1.17.1 and will be in 1.18.0-beta1

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

No branches or pull requests

2 participants