![]() ![]() # Note that for this to work, `persistence.enabled` needs to be set to `true` # Without this, whenever the controller gets restarted (Evicted, etc.) it will fetch plugin updates which has the potential to cause breakage. # Enable to initialize the Jenkins controller only once on initial installation. # List of plugins to install in addition to those listed in controller.installPlugins # Set to false to download the minimum required version of all dependencies. # - kubernetes-credentials-provider:latest # List of plugins to be install during Jenkins controller start # Optionally configure other ports to expose in the controller container # Used to create Ingress record (should used with ServiceType: ClusterIP) # /aws-load-balancer-backend-protocol: https # Use ClusterIP if your setup includes ingress controller # For minikube, set this to NodePort, elsewhere use LoadBalancer # it might be desirable to use `supplementalGroups` instead of `fsGroup` in In the case of mounting an ext4 filesystem, # values provided for the deprecated fields: `runAsUser`, `fsGroup`, and # Completely overwrites the contents of the `securit圜ontext`, ignoring the # If you have PodSecurityPolicies that require dropping of capabilities as suggested by CIS K8s benchmark, put them here # When setting runAsUser to a different value than 0 also set fsGroup to the same value: # Set runAsUser to 1000 to let Jenkins run as non-root user 'jenkins' which exists in 'jenkins/jenkins' docker image. # being deprecated and replaced by `podSecurit圜ontextOverride`. # Note that `runAsUser`, `fsGroup`, and `securit圜ontextCapabilities` are # Enable pod security context (must be `true` if podSecurit圜ontextOverride, runAsUser or fsGroup are set) # If you set this prefix and use ingress controller then you might want to set the ingress path below # If you are not using the provided ingress you can specify `controller.jenkinsUrl` to change the url definition. # The Protocol can be overwritten by specifying `controller.jenkinsUrlProtocol`. # If you are using the ingress definitions provided by this chart via the `controller.ingress` block the configured hostname will be the ingress hostname starting with ` or ` depending on the `tls` configuration. # Environment variables that get added to the init container (useful for e.g. JenkinsWar: "/usr/share/jenkins/jenkins.war" # Path to the jenkins war file which is used by jenkins-plugin-cli. # Cloudbees Jenkins Distribution docker, you should set jenkinsRef: "/usr/share/cloudbees-jenkins-distribution/ref" # Cloudbees Jenkins Distribution docker, you should set jenkinsHome: "/var/cloudbees-jenkins-distribution" ![]() # This values should not be changed unless you use your custom image of jenkins or any devired from. # you should revert controller.adminUser to your preferred admin user: # If you disable the non-Jenkins identity store and instead use the Jenkins internal one, ![]() # When enabling LDAP or another non-Jenkins identity source, the built-in admin account will no longer exist. ![]() # If you don't need that user or use a different security realm then you can disable it # The default configuration uses this secret to configure an admin user # This is ignored if enableRawHtmlMarkupFormatter is true # configures the executor mode of the Jenkins node. # Optionally configure lifetime for controller-container Change this value to match your existing configuration. # For FQDN resolving of the controller service. # Declare name/value pairs to be passed into your templates. There might be redundant parts like that podTemplates: with docker config(copied it from some github repo) and agent: volumes: where I mount the same thing /var/run/docker.sock I don't understand where it should go. Here's the latest one(I removed the ingress part). I tried experimenting with multiple values.yaml variations with no luck. There was also another error Caused: java.io.IOException: Cannot run program "docker": error=2, No such file or directory Docker was installed on host with sudo apt install docker-ce docker-ce-cli containerd.io var/jenkins_home/workspace/ /durable-23187d38/script.sh: 2: /var/jenkins_home/workspace/ /durable-23187d38/script.sh: docker: not found The problem is it does't build docker images, saying there's no docker. I used the following helm chart to install Jenkins ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |