-
-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add a new private kubernetes cluster in the new sponsored azure subscription #3923
Comments
Update: proposal for the new AKS cluster to be soon created:
EDIT: |
…nts (#715) as per jenkins-infra/helpdesk#3923 (comment) kubernetes cluster within the sponsored subscription of azure split in 3 PR: - creation of the cluster (this one) - creation of the nodes - creation of kubernetes-admin-sa with the module depends on jenkins-infra/azure-net#249 for the network definition
the only expected "application" is the Datadog's cluster-agent (2 pods). We should reuse the system pool to run it as it's not an heavy consumer: confirmed by checking the load on the ci.jenkins.io-agents-1 cluster with the same kind of node pool. TODO: add taint toleration to allow datadog cluster-agent to spawn on the system pool |
as per jenkins-infra/helpdesk#3923 and following #715 this PR create 3 nodes pools: - application one in arm64 - agents in x86-64 - agents in arm64 --------- Co-authored-by: Damien Duportal <[email protected]>
datadog namespace created manually:
|
Reopening: The cluster is not used by infra.ci yet |
…each aks api (#735) as per jenkins-infra/helpdesk#3923 we need to allow new agents from the cluster `infracijenkinsioagents1` to access aks api for privatek8s and publick8s.
We had to :
|
…o 1 for ARM64 node pool to avoid slow auto-scaling (#746) Ref. jenkins-infra/helpdesk#3923
Update: infra.ci.jenkins.io is now using the new cluster.
=> All Kubernetes, Terraform and Website jobs are green |
Keeping the issue opened for the week end. Some cleanup might be needed, but CDF is not paying anymore for these agents! |
Related to jenkins-infra/helpdesk#3923, This PR removes the 2 infra.ci agent node pools (now unused) Signed-off-by: Damien Duportal <[email protected]>
Update: a bit of cleanup with jenkins-infra/azure#747 and jenkins-infra/kubernetes-management#5343 |
Closing as it works as expected |
Service(s)
Azure, infra.ci.jenkins.io
Summary
as per #3918 (comment)
ci.jenkins.io
to the sponsored subscription #3913arm64
(controller and agents) #3823=> Let's scope the initial implementation to only infra.ci.jenkins.io agents, and only 1 "non system" nodepool of type linux/arm64 so we can start switching workloads out of privatek8s.
add a new AKS cluster only for infra.ci.jenkins.io and release.ci.jenkins.io Kubernetes agents
private + public ingress, cert-manager,datadog,falco)use the new cluster from infra.ci.jenkins.io
migration/cleanup during this time:
kubernetes-infrasicjio-agents1
kubernetes
cloud from infra.ci to avoid consumingDefinition of done
when the cost will be moved from the CDF payed account to the sponsored one
The text was updated successfully, but these errors were encountered: