Details
-
Type:
Epic
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Component/s: azure
-
Labels:
-
Epic Name:AKS
-
Similar Issues:
Description
Azure Container Service will be retired on January 31, 2020. It is recommended that you migrate your Kubernetes cluster to Azure Kubernetes Service before that date.
Since ACS is deprecated by Azure in favor of AKS, we must deploy a new kubernetes cluster on AKS to brings following major features:
- Cluster upgrade
- Advanced networking configuration
- Recent Kubernetes version
Attachments
Issue Links
- is related to
-
INFRA-2302 Design && Implement RBAC for our azure account
-
- Closed
-
Activity
I'd really like to help on either k8s for master and agents for ci.j.io or getting k8s for agents. I think we have docker images for all of the agents that would be needed. I don't know k8s at all, but would like to learn and help.
Reach out to Vincent Latombe & me for assistance / advice on using the kubernetes plugin. Supposedly we can use ACI to autoscale though I have no experience with this.
Judging by this we have just a week to migrate?!
There's only the azure repo cache left running on the cluster AFAIK.
I don't believe any existing agents run on cluster but it would be good to
I am closing this ticket as the old cluster is now deleted, I'll send an email on the dev mailing to discuss about ci.jenkins.io and how we can improve it
Don't get me wrong, I would be totally in favor of having everything on k8s
It's just a matter of priorities, between ci.jenkins.io and all the other services that require maintenance.
We have a clear and well-known process to maintain ci.jenkins.io master but it's a totally different story for the agent