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

[Spike] Move affinity block to values #45516

Open
MKlimuszka opened this issue May 16, 2024 · 0 comments
Open

[Spike] Move affinity block to values #45516

MKlimuszka opened this issue May 16, 2024 · 0 comments
Labels
area/helm feature/rancher-server-helm-chart internal kind/enhancement Issues that improve or augment existing functionality team/observability&backup the team that is responsible for monitoring/logging and BRO

Comments

@MKlimuszka
Copy link
Collaborator

MKlimuszka commented May 16, 2024

Research spike to determine feasibility and loe for this feature.

Request description:

Improve the helm chart features for rancher

Actual behavior:

Unable to set affinities for rancher pod outside of a hardcoded definition
Unable to set tolerations for rancher pod
Unable to set nodeSelector for rancher pod
Unable to set resources for the audit logs sidecar

Expected behavior:

Give the ability to set affinities for rancher pod
Give the ability to set tolerations for rancher pod
Give the ability to set nodeSelector for rancher pod
Give the ability to set resources for the audit logs sidecar

Original reporter is willing to open a PR, but we need to know if that's advisable.
SURE-6244

@MKlimuszka MKlimuszka added area/helm feature/rancher-server-helm-chart internal kind/enhancement Issues that improve or augment existing functionality team/observability&backup the team that is responsible for monitoring/logging and BRO labels May 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/helm feature/rancher-server-helm-chart internal kind/enhancement Issues that improve or augment existing functionality team/observability&backup the team that is responsible for monitoring/logging and BRO
Projects
None yet
Development

No branches or pull requests

1 participant