Skip to content
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

[get.jenkins.io] migrate from mirrorbits to mirrorbits-parent chart #3828

Closed
dduportal opened this issue Nov 22, 2023 · 11 comments
Closed

[get.jenkins.io] migrate from mirrorbits to mirrorbits-parent chart #3828

dduportal opened this issue Nov 22, 2023 · 11 comments

Comments

@dduportal
Copy link
Contributor

Service(s)

Azure, get.jenkins.io

Summary

Following the work done in #3619 and #2649 , we have to update the service get.jenkins.io in jenkins-infra/kubernetes-management to use the mirrorbits-parent chart instead of the current (and soon to be removed) mirrorbits.

  • It will allows us to use the latest improvements we did on the chart and config management (logs mangement, debugging mirrorbits, umbrella storage and ingress, etc.)
  • It will allows migrating the httpd server to arm64 for get.jenkins.io

Reproduction steps

No response

@dduportal
Copy link
Contributor Author

Preliminary step: defines archives.jenkins.io as fallback instead of the 2 OSUOSL:

@dduportal
Copy link
Contributor Author

Preliminary step: defines archives.jenkins.io as fallback instead of the 2 OSUOSL:

* Since [Move archives.jenkins.io service away from Oracle #3760](https://github.com/jenkins-infra/helpdesk/issues/3760), archives.jenkins.io runs in DigitalOcean (in Frakfurt, Germany, datacenter) and the download bandwitdh is good and cheap

* As pert [In reference to issue #3183 #3338](https://github.com/jenkins-infra/helpdesk/issues/3338) (and many other issues), OSUOSL seems to purge some data after some time while archives.jenkins.io does not

@dduportal
Copy link
Contributor Author

Update:

@dduportal
Copy link
Contributor Author

Update:

Todo:

  • Manual operation: for migration:
    • Set up to proper domains and RedisDB on the new get.jenkins.io
    • Remove ingress of mirrorbits
    • Scale mirrorbits to zero
  • Validate: if it works, then remove namespace and config for old mirrorbits, otherwise rollback

@dduportal
Copy link
Contributor Author

Update:

@dduportal
Copy link
Contributor Author

Update:

  • jenkins-infra/kubernetes-management is OK for get-jenkins-io
  • Removed the former PV mirrorbits-binary

Todo:

  • Cleanupo helm-charts repository and updatecli manifests

@lemeurherve
Copy link
Member

Cleanupo helm-charts repository and updatecli manifests

Will it include the renaming of mirrorbits-parent to mirrorbits? (Please say yes ^^)

@dduportal
Copy link
Contributor Author

Cleanupo helm-charts repository and updatecli manifests

Will it include the renaming of mirrorbits-parent to mirrorbits? (Please say yes ^^)

mirrorbits-lite by mirrorbits you mean? ;)

@dduportal
Copy link
Contributor Author

Update (cleanup mirrorbits):

Todo:

  • wait for the 2.0.0 release of mirrorbits-parent in jenkins-infra/kubernetes-management
  • change chart values and deploy it

@dduportal
Copy link
Contributor Author

Update:

ToDo:

  • Deploy this chart (will most probably cause a downtime)

@dduportal
Copy link
Contributor Author

Update:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants