Uploaded image for project: 'Infrastructure'
  1. Infrastructure
  2. INFRA-2918

Setup ci.jenkins.io Kubernetes agents along with ACI containers

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      The goal is to add to ci.jenkins.io the same workload capability as ACI agents provides but with Kubernetes agents.

      • Ref. INFRA-2919 : Kubernetes is configured with an AWS EKS cluster
      • Why? ACI cost a kidney, and are a liability. Merging workloads to a static Kube cluster would allow a static build capability to decrease the infra cost, and keeping ACI for "peaks" in the build queue

      This changes leads to the depreciation of the attribute useAci for the pipeline library function `buildPlugin()` (see PR on the library at https://github.com/jenkins-infra/pipeline-library/pull/220).

      If you land on this page because of a deprecation message: please edit the file Jenkinsfile at the root of your repository and replace the atrribute useAci by useContainerAgent.

        Attachments

          Issue Links

            Activity

            dduportal Damien Duportal created issue -
            dduportal Damien Duportal made changes -
            Field Original Value New Value
            Summary Migrate ci.jenkins.io back to Kubernetes Setup ci.jenkins.io Kubernetes agents along with ACI containers
            dduportal Damien Duportal made changes -
            Description Following up https://issues.jenkins.io/browse/INFRA-2917 , the goal would be to migrate ci.jenkins.io inside a full Kubernetes's controller

            * (x) Define Kubernetes cluster where to run
            * (x) Define the sizing and container settings (limits, JVM opts, disk storage, etc.)
            * (x) Add the initial helmfile into jenkins-infra/charts (preliminary try by [~timjacomb] in https://github.com/jenkins-infra/charts/pull/174)
            * (x) SHIP IT
            The goal is to add to ci.jenkins.io the same workload capability as ACI agents provides but with Kubernetes agents.

            * Ref. INFRA-2919 : Kubernetes is configured with an AWS EKS cluster
            * Why? ACI cost a kidney, and are a liability. Merging workloads to a static Kube cluster would allow a static build capability to decrease the infra cost, and keeping ACI for "peaks" in the build queue
            dduportal Damien Duportal made changes -
            Status Open [ 1 ] In Progress [ 3 ]
            dduportal Damien Duportal made changes -
            Rank Ranked higher
            dduportal Damien Duportal made changes -
            Link This issue relates to INFRA-3030 [ INFRA-3030 ]
            dduportal Damien Duportal made changes -
            Resolution Fixed [ 1 ]
            Status In Progress [ 3 ] Resolved [ 5 ]
            dduportal Damien Duportal made changes -
            Status Resolved [ 5 ] Closed [ 6 ]
            dduportal Damien Duportal made changes -
            Resolution Fixed [ 1 ]
            Status Closed [ 6 ] Reopened [ 4 ]
            dduportal Damien Duportal made changes -
            Status Reopened [ 4 ] In Progress [ 3 ]
            dduportal Damien Duportal made changes -
            Description The goal is to add to ci.jenkins.io the same workload capability as ACI agents provides but with Kubernetes agents.

            * Ref. INFRA-2919 : Kubernetes is configured with an AWS EKS cluster
            * Why? ACI cost a kidney, and are a liability. Merging workloads to a static Kube cluster would allow a static build capability to decrease the infra cost, and keeping ACI for "peaks" in the build queue
            The goal is to add to ci.jenkins.io the same workload capability as ACI agents provides but with Kubernetes agents.

            * Ref. INFRA-2919 : Kubernetes is configured with an AWS EKS cluster
            * Why? ACI cost a kidney, and are a liability. Merging workloads to a static Kube cluster would allow a static build capability to decrease the infra cost, and keeping ACI for "peaks" in the build queue

            This changes leads to the depreciation of the attribute `useAci` for the pipeline library function `buildPlugin()` (see PR on the library at https://github.com/jenkins-infra/pipeline-library/pull/220)
            dduportal Damien Duportal made changes -
            Description The goal is to add to ci.jenkins.io the same workload capability as ACI agents provides but with Kubernetes agents.

            * Ref. INFRA-2919 : Kubernetes is configured with an AWS EKS cluster
            * Why? ACI cost a kidney, and are a liability. Merging workloads to a static Kube cluster would allow a static build capability to decrease the infra cost, and keeping ACI for "peaks" in the build queue

            This changes leads to the depreciation of the attribute `useAci` for the pipeline library function `buildPlugin()` (see PR on the library at https://github.com/jenkins-infra/pipeline-library/pull/220)
            The goal is to add to ci.jenkins.io the same workload capability as ACI agents provides but with Kubernetes agents.

            * Ref. INFRA-2919 : Kubernetes is configured with an AWS EKS cluster
            * Why? ACI cost a kidney, and are a liability. Merging workloads to a static Kube cluster would allow a static build capability to decrease the infra cost, and keeping ACI for "peaks" in the build queue

            This changes leads to the depreciation of the attribute `useAci` for the pipeline library function `buildPlugin()` (see PR on the library at https://github.com/jenkins-infra/pipeline-library/pull/220).

            If you land on this page because of a deprecation message: please edit the file `Jenkinsfile` at the root of your repository and replace the atrribute `useAci` by `useContainerAgent`. It's only a name change: there are no functionnal changes.
            dduportal Damien Duportal made changes -
            Description The goal is to add to ci.jenkins.io the same workload capability as ACI agents provides but with Kubernetes agents.

            * Ref. INFRA-2919 : Kubernetes is configured with an AWS EKS cluster
            * Why? ACI cost a kidney, and are a liability. Merging workloads to a static Kube cluster would allow a static build capability to decrease the infra cost, and keeping ACI for "peaks" in the build queue

            This changes leads to the depreciation of the attribute `useAci` for the pipeline library function `buildPlugin()` (see PR on the library at https://github.com/jenkins-infra/pipeline-library/pull/220).

            If you land on this page because of a deprecation message: please edit the file `Jenkinsfile` at the root of your repository and replace the atrribute `useAci` by `useContainerAgent`. It's only a name change: there are no functionnal changes.
            The goal is to add to ci.jenkins.io the same workload capability as ACI agents provides but with Kubernetes agents.

            * Ref. INFRA-2919 : Kubernetes is configured with an AWS EKS cluster
            * Why? ACI cost a kidney, and are a liability. Merging workloads to a static Kube cluster would allow a static build capability to decrease the infra cost, and keeping ACI for "peaks" in the build queue

            This changes leads to the depreciation of the attribute {{useAci}} for the pipeline library function `buildPlugin()` (see PR on the library at https://github.com/jenkins-infra/pipeline-library/pull/220).

            If you land on this page because of a deprecation message: please edit the file {{Jenkinsfile}} at the root of your repository and replace the atrribute {{useAci}} by {{useContainerAgent}}.
            * It's only a name change: there are no functionnal changes.
            * You can find an example change on the following pull request: https://github.com/jenkinsci/jenkins-infra-test-plugin/pull/12
            dduportal Damien Duportal made changes -
            Link This issue relates to INFRA-2059 [ INFRA-2059 ]
            dduportal Damien Duportal made changes -
            Rank Ranked higher
            ponch F Ponciroli made changes -
            Resolution Fixed [ 1 ]
            Status In Progress [ 3 ] Resolved [ 5 ]
            ponch F Ponciroli made changes -
            Resolution Fixed [ 1 ]
            Status Resolved [ 5 ] Reopened [ 4 ]
            dduportal Damien Duportal made changes -
            Resolution Fixed [ 1 ]
            Status Reopened [ 4 ] Closed [ 6 ]

              People

              Assignee:
              dduportal Damien Duportal
              Reporter:
              dduportal Damien Duportal
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: