Add optional hostUsers field to the KEDA pods#880
Open
somaz94 wants to merge 1 commit into
Open
Conversation
… pods Signed-off-by: somaz <genius5711@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds an opt-in
hostUsersfield to the operator, metrics server and admissionwebhooks pods so KEDA's components can run in their own user namespace
(graduated in Kubernetes 1.36). Mirrors the existing
useHostNetworktoggle.Unset by default, so existing renders are byte-identical; setting
operator.hostUsers/metricsServer.hostUsers/webhooks.hostUserstotrueorfalseemits the field on the matching pod only.Validation (local)
helm lint keda: 0 failedhelm template: default omits the field (no diff for current users); set tofalse/truerenders it on the correct pod(s) onlyhelm installon a kind v1.34 cluster withhostUsers=true: operator, metricsserver and webhooks pods all Running, field present on the live pod specs
hostUsers=false(deployment + new ReplicaSet created);running a pod with
falseadditionally needs the node to support user namespacesChecklist
Fixes #879