[Jenkins-infra] Kubernetes and Evergreen status?

[Olblak]

Hey,

As some of you already know, one of the two Kubernetes clusters used by the Jenkins infrastructure project will be stopped by Azure on the 31st of January 2020, this means that every website running on it need to be transferred on our new AKS cluster <https://github.com/jenkins-infra/azure/blob/master/plans/publick8s.tf> before that date.

We have a Jira epic to keep track of this work INFRA-1797 <https://issues.jenkins-ci.org/browse/INFRA-1797>
---

INFRA-2357 <https://issues.jenkins-ci.org/browse/INFRA-2357>
Move plugins.jenkins.io to new Kubernetes Charts
Improvement
Resolved
Tim Jacomb <https://issues.jenkins-ci.org/secure/ViewProfile.jspa?name=timja>


INFRA-2359 <https://issues.jenkins-ci.org/browse/INFRA-2359>
Move javadoc.jenkins.io to new Kubernetes Charts
Story
Resolved
Tim Jacomb <https://issues.jenkins-ci.org/secure/ViewProfile.jspa?name=timja>


INFRA-2360 <https://issues.jenkins-ci.org/browse/INFRA-2360>
Move accounts.jenkins.io to new Kubernetes Charts
Story
In Progress
Tim Jacomb <https://issues.jenkins-ci.org/secure/ViewProfile.jspa?name=timja>


INFRA-2361 <https://issues.jenkins-ci.org/browse/INFRA-2361>
Move jenkins.io to new Kubernetes Charts
Story
In Progress
Tim Jacomb <https://issues.jenkins-ci.org/secure/ViewProfile.jspa?name=timja>


INFRA-2362 <https://issues.jenkins-ci.org/browse/INFRA-2362>
Move evergreen.jenkins.io to new Kubernetes Charts
Story
Open
*Unassigned*


INFRA-2363 <https://issues.jenkins-ci.org/browse/INFRA-2363>
Move uplink.jenkins.io to new Kubernetes Charts
Story
Open
*Unassigned*


INFRA-2364 <https://issues.jenkins-ci.org/browse/INFRA-2364>
Move ldap.jenkins.io to new Kubernetes Charts
Story
Open
*Unassigned*


INFRA-2365 <https://issues.jenkins-ci.org/browse/INFRA-2365>
Move reports.jenkins.io to new Kubernetes Charts
Story
In Progress
Tim Jacomb <https://issues.jenkins-ci.org/secure/ViewProfile.jspa?name=timja>


INFRA-2366 <https://issues.jenkins-ci.org/browse/INFRA-2366>
Move jenkins admin chatbot to new Kubernetes Charts
Story
In Progress
Tim Jacom <https://issues.jenkins-ci.org/secure/ViewProfile.jspa?name=timja>
 ---

As you can see a lot of work has already been done by Tim Jacob, big thanks for his help, but we still have some services that need to be move and especially I am looking for feedbacks regarding *evergreen*, is it a service that we should keep maintaining, and if yes who would volunteer to maintain that application?

We are also taking the opportunity to simplify the way we manage websites running on Kubernetes by moving from puppet <https://github.com/jenkins-infra/jenkins-infra/tree/staging/dist/profile/manifests/kubernetes> to helmfile. <https://github.com/jenkins-infra/charts> We are trying a different approach to give back service maintenance responsibilities to the community by having different codeowners per application, basically, as a codeowner you are responsible to maintain the helm chart associated to a specific service and also review and merge any PR related to that service.

An example is plugins.jenkins.io
* An application defined by this helm chart <https://github.com/jenkins-infra/charts/tree/master/charts/plugin-site>
* Deployed using helmfile <https://github.com/jenkins-infra/charts/blob/master/clusters/publick8s.yaml#L20> and sop  <https://github.com/jenkins-infra/charts/blob/master/.sops.yaml#L23-L15>
* Maintained by codeowner <https://github.com/jenkins-infra/charts/blob/master/CODEOWNERS#L12-L11>

While looking for service maintainers, we are also looking for suggestions to improve the process.

Cheers


---
gpg --keyserver keys.gnupg.net --recv-key 52210D3D
---
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.jenkins-ci.org/pipermail/jenkins-infra/attachments/20191216/1cbd55f2/attachment.html>