-
Notifications
You must be signed in to change notification settings - Fork 103
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
[task] pre-work 24.04 lts stemcell release #294
Comments
I thought the point of jumping to 22.04 was to stick with that until 26.04. If CF runs only on newer stemcells, FIPS compliance will always be out of reach. |
The question is how long can we support the older versions? Can we provide the complete stack on 2 or 3 stemcells before their standard support ends? |
What @max-soe mentioned is one of the issues we noticed with the four years cycle. Regarding FIPS it is also a challenge because Ubuntu Bionic is EoL but there is no FIPS certified Ubuntu Jammy. With a two years cycle the users could stay on the old FIPS certified stemcell line until the new one gets it, which we hope will be before EoL of the old one. This is a discussion which have to happen in the CFF community via an RFC so that we have a decision. There is nothing concrete yet. |
there will always only be 2 LTS releases supported within the support window of canonical so the idea is to keep up to date with all the supported LTS releases. which will be max 2 at a time. as beyhan mentioned FIPS is a thing on its own and will have different release cycles. pipelines etc, |
Between bionic and jammy there is also Focal Fossa. So if we now update every 2 years, we must support 3 LTS. |
We have different options here and we should analyse all of them and compare but I don't think that this issue is the right place. I will prefer an RFC for this so that we get more brother feedback. |
this can be closed see cloudfoundry/community#892 |
as ubuntu lts releases are created every 2 years. we should also keep up with there release cycle.
its still a year away. but maby we need to do some pre-work
investigate and readup on the changes to come for 23.04/10
The text was updated successfully, but these errors were encountered: