Uploaded image for project: 'Nuxeo ECM Build/Test Environment'
  1. Nuxeo ECM Build/Test Environment
  2. NXBT-3403

Run the JX Napps builds on a dedicated Kubernetes node pool

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Jenkins X
    • Environment:
      Kubernetes
      JX
    • Tags:
    • Impact type:
      Configuration Change
    • Sprint:
      nxApps 2020 Cycle 10
    • Story Points:
      3

      Description

      Unfortunately, tolerations cannot be defined through values.yaml because the Kubernetes plugin for
      Jenkins doesn't take them into account when reading a pod template.
      The solution is to use a `yaml` field in the pod template, yet it isn't taken into account by the Jenkins-x-platform chart.

      • Create a new node pool

      Add a node pool:

      https://console.cloud.google.com/kubernetes/clusters/details/us-east1-b/jx-prod?project=jx-preprod&tab=details
      https://console.cloud.google.com/kubernetes/nodepool/us-east1-b/jx-prod/pool-team-napps?project=jx-preprod

      • Autoscalling: On (0-8 nodes)
      • Image type: Container-Optimized OS (cos)
      • Machine type: e2-standard-8
      • Kubernetes labels: team: napps
      • Taints: NoSchedule team=napps
      • Update the pod template

      In the Pod Template definitions, use a NodeSelector to match the team.

      Use the n'Apps team node pod-team-napps with this spec:

          tolerations:
            - key: team
              operator: Equal
              value: napps
              effect: NoSchedule
          nodeSelector:
            team: napps 

       
      All the custom Jenkins pod templates are now configured to run on  pod-team-napps.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 4 hours
                  4h

                    PagerDuty