Repository navigation
Conversation
…xamples Mirrors the fix applied to flow-on-kubernetes/examples/ (CDRO-17580). Both OpenShift reference values files were missing this required setting, which causes a hard Helm render failure on any OpenShift cluster (_helpers.tpl fails with "Please make boundAgent.volumePermissions.enabled=false to install/upgrade on OpenShift platform").
…t that actually runs The existing dois openshiftNodeTuning/sysctlInitContainer override in both OpenShift example files was set on the wrong key: dois.enabled is false by default, so that statefulset never renders. analytics is the component that actually always deploys, and its sysctlInitContainer is a *privileged* init container (sets vm.max_map_count) -- confirmed via `helm template` that OpenShift's default restricted SCC would reject it without this override. Left the existing (harmless but inert) dois block in place.
Muxamedin
force-pushed
the
CDRO-17580-openshift-examples-fix
branch
from
October 6, 2026 15:55
d99e056 to
46550f1
Compare
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
1 participant
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.
Summary
cloudbees-cd-{demo,prod}-openshift.yamlwere missingboundAgent.volumePermissions.enabled: false— the chart's_helpers.tplhard-fails Helm render on any OpenShift cluster without it ("Please make boundAgent.volumePermissions.enabled=false to install/upgrade on OpenShift platform").openshiftNodeTuning/sysctlInitContaineroverride in both files was set underdois:, a component that's disabled by default (dois.enabled: false) and never renders.analyticsis the component that actually always deploys, and itssysctlInitContaineris a privileged init container — confirmed viahelm templatethat it would be rejected by OpenShift's default restricted SCC without this override.Found and verified while validating CD/RO on OpenShift 4.22 (CDRO-17580) — same two issues were also fixed in
electric-cloud/flow-on-kubernetes/examples/.Test plan
helm templatewith--api-versions route.openshift.io/v1: fails withoutboundAgent.volumePermissions.enabled: false, passes with ithelm template -s templates/analytics-stateful-set.yaml: privilegedsysctlinit container present with chart defaults, absent withanalytics.sysctlInitContainer.enabled: false