Comments (9)
Has there been any thought to any sort of release schedule for BottleRocket? A lot of us run things like Karpenter, which will start rotating nodes very quickly after release. I guess I'm not thinking anything super formal, more just a 'tomorrow at 4pm we plan to release bottle rocket x.yy.zz"
from bottlerocket.
v1.19.2 has selinux permission issue with s3-csi-driver: awslabs/mountpoint-s3-csi-driver#160
from bottlerocket.
Please feel free to read over, adjust, or close if it's not appropriate.
from bottlerocket.
This release has been completed on 26th Feb, 2024.
from bottlerocket.
@misterek Bottlerocket's release process is pretty complex, so it's tricky to provide an answer as you suggested, but here goes:
- there is an approximate 6-8 week cycle for minor releases (x.+.x).
- Patches/bug fixes (x.x.+) are off cycle and come as soon as possible (and, depending on the severity, it can be accelerated ).
- The project can't give a deterministic answer of when a release will be available for everyone because:
- for those using in-place, update waves mean that nodes get updates at different times,
- for those using node replacement, updates rely on SSM parameters which hit different regions at different times.
- On GitHub the last thing that happens is merging the changelog - that's the last signal publicly before starting the release, but it still can take approximately 24-72 hours after that. That delay is unpredictable.
As for timing, most releases tend to complete late in the work day US pacific time.
There are some immovable objects in this process, but glad to hear any feedback on what you'd need.
from bottlerocket.
Thanks for the context @stockholmux !
I perhaps conflated a couple things -- the release and updating the AMI. The AMI update is really the part that I was referring to.
Specifically, where my thinking was is bullet point 3, and in this case, the node replacement. With the last release, nodes were being replaced 5-10 minutes before the GitHub Release was posted. Which, in many respects, was super cool.
I think my dream would be different SSM Parameters that are offset by days, with matching configuration options in Karpenter. i.e. "1 day after release", "5 days after release" "7 days after release". So you could configure dev, qa, and prod to each apply the updates at a differing amount of times after release. To be fair, i think there's only been one release where there's been a problem (1.13), but that'd be a good mix between "update ASAP", and "Allow some soak in time for a release", without having to manage updates manually.
It's a manageable problem as is, but would be even more convenient if we could automate it like that.
from bottlerocket.
@misterek That seems interesting. Do you want to create a separate issue for that so we can track it as a feature request?
@tanvp112 Looks like the CSI driver had a release that rectifies the situation.
from bottlerocket.
Will do! Thanks @stockholmux
from bottlerocket.
Thanks folks! I'm going to close the issue since we're a couple weeks past the release of 1.19.2
from bottlerocket.
Related Issues (20)
- v1.20.2 🤘🏾 Tracking Issue HOT 1
- Publish AMI IDs for K8s with Nvidia support via public SSM parameters, just like other AMIs HOT 4
- core kit migration 🚧 tracking issue HOT 2
- Potential significant max network throughput performance regression HOT 3
- Create an interface for determining the release date of an update HOT 2
- Add the socat package to Bottlerocket
- Need API Setting to allow modify kubelet config for Json logging format HOT 1
- Allow parallel image pulls HOT 5
- `host-ctr` cli crashes when pulling public ECR image HOT 11
- Add `allow2audit` to images HOT 7
- v1.20.3 🐨 Tracking Issue
- Add Kata Containers to images HOT 2
- `cargo make repo` fails after move to `bottlerocket-core-kit` HOT 4
- `dockershim.sock` symlink should be relative HOT 4
- Unresponsive/unreachable Bottlerocket EKS nodes HOT 18
- Enable PodLifecycleSleepAction HOT 1
- Setting cluster-domain has no effect HOT 2
- SELinux Policy: system_u:system_r:cachefiles_kernel_t:s0 HOT 2
- Remove aws-k8s-1.23 variants by October 2024
- Node doesn't expose GPU resource on g4dn.[n]xlarge HOT 8
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from bottlerocket.