You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I try to install jenkins-operator via Helm chart as described in the documentation with the value imagePullSecrets specified. In my values file I have following option defined.
imagePullSecrets:
- name: "my-nexus-doker-pull"
I get the following error
coalesce.go:199: warning: cannot overwrite table with non table for configurationAsCode (map[])
Error: INSTALLATION FAILED: unable to build kubernetes objects from release manifest: error validating "": error validating data: ValidationError(Jenkins.spec.master.containers[0]): unknown field "imagePullSecrets" in io.jenkins.v1alpha2.Jenkins.spec.master.containers
Describe the bug
I try to install jenkins-operator via Helm chart as described in the documentation with the value
imagePullSecrets
specified. In my values file I have following option defined.I get the following error
To Reproduce
Specify in
values.yaml
the propertyimagePullSecrets
with a certain values instead of the empty array [], which stays there by default. This is an array of items, which have "name" property (see https://github.com/jenkinsci/kubernetes-operator/blob/master/chart/jenkins-operator/crds/jenkins-crd.yaml#L1122)try to setup an operator as described in the documentation
or checkout the source code of the operator and try with specific latest version
Additional information
Kubernetes version: 1.19
Jenkins Operator version: jenkins-operator-0.5.3.tgz
I managed to workaround the problem by fixing
jenkins.yaml
template locally in the chart.The problem is that
imagePullSecrets
is defined incrds/jenkins-crd.yaml
onmaster.properties
level, while intemplates/jenkins.yaml
imagePullSecrets
is defined undermaster.containers
level (see https://github.com/jenkinsci/kubernetes-operator/blob/master/chart/jenkins-operator/templates/jenkins.yaml#L109).So I managed to fix it by moving following part of the template in
templates/jenkins.yaml
one level upper, to the
master
node.The text was updated successfully, but these errors were encountered: