Manage nodes & cloud

Maheshrvm · December 23, 2022, 6:48am

I want to save the changes in configure cloud (Manage Jenkins → Manage Nodes and Clouds → Configure Clouds → Add a new cloud → Kubernetes) permanently, but unfortunately after restart Jenkins/pod changes are reset to default. I wanted to set the kubernetes cluster details, Jenkins URL, port and pod template details in Configure cloud settings. Please suggest how to achieve this to make changes permanently without losing after Jenkins/pod restart.

PierreBtz · January 2, 2023, 2:49pm

How do you start your instance? Are you by any chance using JCasc, in which case it’s expected that any change you make to the UI is lost at restart.

Maheshrvm · January 3, 2023, 4:22am

Its managed by Kubernetes not IaC, yes I did some changes in the UI under configure cloud (manage jenkins>manage nodes&clouds>configure cloud) with my docker image and kubernetes cluster details and pod templates. But unfortunately those chages were set to default when I restart Jenkins on UI or pod restart also. My requirement is the manual changes which are done in configure cloud should persistent permanantly.

PierreBtz · January 3, 2023, 8:51am

Its managed by Kubernetes not IaC

I’m not sure I understand this statement. Did you read the link I sent about JCasc? Can you give more details about your setup?

halkeye · January 3, 2023, 7:17pm

I’ll throw out that helm uses JCasc

github.com

jenkinsci/helm-charts/blob/d0aa61f5921fb937e6f0a75ee3c1cf1f86cd2b18/charts/jenkins/values.yaml#L313-L323


      
          # Name of default cloud configuration.
          cloudName: "kubernetes"
          
          
# Below is the implementation of Jenkins Configuration as Code.  Add a key under configScripts for each configuration area,
          # where each corresponds to a plugin or section of the UI.  Each key (prior to | character) is just a label, and can be any value.
          # Keys are only used to give the section a meaningful name.  The only restriction is they may only contain RFC 1123 \ DNS label
          # characters: lowercase letters, numbers, and hyphens.  The keys become the name of a configuration yaml file on the controller in
          # /var/jenkins_home/casc_configs (by default) and will be processed by the Configuration as Code Plugin.  The lines after each |
          # become the content of the configuration yaml file.  The first line after this is a JCasC root element, eg jenkins, credentials,
          # etc.  Best reference is https://<jenkins_url>/configuration-as-code/reference.  The example below creates a welcome message:
          JCasC:

and the “defaultConfig” for jcasc in helm creates a kubernetes cloud thingie

github.com

jenkinsci/helm-charts/blob/d0aa61f5921fb937e6f0a75ee3c1cf1f86cd2b18/charts/jenkins/templates/_helpers.tpl#L141


      
          {{- end }}
          {{- end }}
          markupFormatter:
            {{- if .Values.controller.enableRawHtmlMarkupFormatter }}
            rawHtml:
              disableSyntaxHighlighting: true
            {{- else }}
            {{- toYaml .Values.controller.markupFormatter | nindent 4 }}
            {{- end }}
          clouds:
          - kubernetes:
              containerCapStr: "{{ .Values.agent.containerCap }}"
              defaultsProviderTemplate: "{{ .Values.agent.defaultsProviderTemplate }}"
              connectTimeout: "{{ .Values.agent.kubernetesConnectTimeout }}"
              readTimeout: "{{ .Values.agent.kubernetesReadTimeout }}"
              {{- if .Values.agent.jenkinsUrl }}
              jenkinsUrl: "{{ tpl .Values.agent.jenkinsUrl . }}"
              {{- else }}
              jenkinsUrl: "http://{{ template "jenkins.fullname" . }}.{{ template "jenkins.namespace" . }}.svc.{{.Values.clusterZone}}:{{.Values.controller.servicePort}}{{ default "" .Values.controller.jenkinsUriPrefix }}"
              {{- end }}
              {{- if not .Values.agent.websocket }}

I’m assuming you are using helm because it sounds like this scenario, and lots of people install jenkins on k8s via helm

Maheshrvm · January 6, 2023, 12:39pm

Yes Halkeye, I am deployed Jenkins on K8s cluster using Helm. My only concern is whenever I have restarted Jenkins/pod whatever the cloud configurations(manage jenkins>manage node &cloud) which I update manually in the UI gets reset to default. We want this changes permanent so that our pipelines don’t get failed. Thanks.!!

PierreBtz · January 6, 2023, 1:53pm

As explained by @halkeye and myself, this is the expected behaviour when using Jcasc. You’ll have to update your Jcasc configuration since changes in the UI won’t be persisted.

If you don’t know which properties to modify in your JCasc config:

perform the change in the UI
export the configuration as explained in this document
by diffing the export and your current configuration you should find what to change

Maheshrvm · January 6, 2023, 3:48pm

Thank you.! I will update Jcasc config.

Topic		Replies	Views
Jenkins CaSC - Kubernetes Using Jenkins	2	78	October 7, 2024
Loss of configuration after Jenkins restart Ask a question	4	4012	October 19, 2023
Kubernetes Cloud Configuration in Jenkins: Continuous Pod Creation and Unknown Client Name Error Ask a question kubernetes	1	1803	August 24, 2023
Jenkins SSO Issue after restart in GKE Using Jenkins	2	20	November 6, 2024
GitHub Authentication reset after jenkins restart Ask a question	2	915	March 15, 2023

Manage nodes & cloud

Related topics