Bumping helm chart dependency versions: support#3482
Merged
Conversation
…caler', 'cryptnono'] to versions ['25.8.0', '7.0.11', '4.8.3', '9.32.1', '0.3.0'], respectively
Contributor
|
Merging this PR will trigger the following deployment actions. Support and Staging deployments
Production deploymentsNo production hub upgrades will be triggered |
yuvipanda
previously requested changes
Dec 5, 2023
Member
yuvipanda
left a comment
yuvipanda
left a comment
There was a problem hiding this comment.
cryptnono has breaking changes so let's hold this for a bit
…yptnono'] to versions ['25.8.1', '4.8.4', '9.34.0', '0.3.1-0.dev.git.90.h35abda8'], respectively
…caler', 'cryptnono'] to versions ['25.8.2', '7.0.19', '4.9.0', '9.34.1', '0.3.1-0.dev.git.107.heb504bc'], respectively
yuvipanda
added a commit
to yuvipanda/pilot-hubs
that referenced
this pull request
Jan 4, 2024
I've been upgrading cryptnono quite a bit over the last few months, bringing in new detectors that have been quite effective on mybinder.org. We automatically bump cryptnono on our clusters (2i2c-org#3482), but recent progress have included some breaking changes to the helm chart config. This PR just brings in the new config changes, but does not change behavior in any real way. No new detectors are enabled. I've re-measured resource usage for the individual daemonset container (rather than the initContainer) as that can now be set separately. This probably requires us to redo some of the resource allocation generated profiles, which I'll do once this is merged. However, it is an overall reduction in daemonset requests, so deploying this shouldn't result in any profile being undeployable. Merging this should allow 2i2c-org#3482 to move forward as well.
Member
|
This can proceed now, as cryptnono's breaking changes were addressed by #3569 |
…ev.git.129.ha9d73b8'], respectively
yuvipanda
reviewed
Jan 17, 2024
Member
|
I tried this out locally, but fails with: |
Member
|
This is a little annoying because we do encrypt them already. |
yuvipanda
reviewed
Jan 17, 2024
Member
|
It's important to keep this moving so our version bumps don't become too big, so am testing this out and will upgrade everything except grafana. |
Member
|
I've manually tested this on one cluster on each cloud provider, and it seems all good. |
Contributor
|
🎉🎉🎉🎉 Monitor the deployment of the hubs here 👉 https://github.com/2i2c-org/infrastructure/actions/runs/7549375512 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Upgrading most support components, except Grafana (due to some breaking changes)