Update cflinuxfs from version 3 to version 4 with optional 5#1104
Open
jakweg wants to merge 5 commits into
Open
Update cflinuxfs from version 3 to version 4 with optional 5#1104jakweg wants to merge 5 commits into
cflinuxfs from version 3 to version 4 with optional 5#1104jakweg wants to merge 5 commits into
Conversation
jakweg
force-pushed
the
jakweg_cflinuxfs_update
branch
15 times, most recently
from
49a85b8 to
db7e4c7
Compare
jakweg
force-pushed
the
jakweg_cflinuxfs_update
branch
3 times, most recently
from
53003f8 to
7d19b47
Compare
jakweg
changed the title
cflinuxfs3 references to cflinuxfs5cflinuxfs from version 3 to version 4 with optional 5
jakweg
force-pushed
the
jakweg_cflinuxfs_update
branch
4 times, most recently
from
6a274f3 to
1647619
Compare
jakweg
force-pushed
the
jakweg_cflinuxfs_update
branch
4 times, most recently
from
956d202 to
bfe8e75
Compare
jakweg
force-pushed
the
jakweg_cflinuxfs_update
branch
2 times, most recently
from
e3a0b65 to
c271872
Compare
jakweg
force-pushed
the
jakweg_cflinuxfs_update
branch
3 times, most recently
from
1ba5822 to
df94fe0
Compare
jakweg
force-pushed
the
jakweg_cflinuxfs_update
branch
from
df94fe0 to
d2f2406
Compare
jakweg
force-pushed
the
jakweg_cflinuxfs_update
branch
from
d2f2406 to
a2e38eb
Compare
| cbnPlatformApiEnv := []corev1.EnvVar{ | ||
| { | ||
| Name: "CNB_PLATFORM_API", | ||
| Value: "0.15", |
Contributor
There was a problem hiding this comment.
Is this value hardcoded or the users can override it somehow?
Contributor
Author
There was a problem hiding this comment.
Currently no, adding ability to override with -env variable
jakweg
force-pushed
the
jakweg_cflinuxfs_update
branch
from
a2e38eb to
a2a5bb2
Compare
balamut-google
approved these changes
May 15, 2026
jakweg
force-pushed
the
jakweg_cflinuxfs_update
branch
from
a2a5bb2 to
8c02db3
Compare
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
2 participants
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.
Proposed Changes
cflinuxfs3references tocflinuxfs4andcflinuxfs5. KF now defaults tocflinuxfs4instead ofcflinuxfs3.Release Notes
Before updating
The new stack is based on
Ubuntu 22.04by default, orUbuntu 24.04if you opt intocflinuxfs5, which is significantly newer than the currentUbuntu 18.04. Before updating, ensure your application does not depend on utilities or libraries that behave differently in newer Ubuntu versions. Newer stack means newer buildpacks platforms, kf now usesCNB_PLATFORM_API=0.15for all builds (unless running on legacy stack). You can override this behavior during pushkf push (...) -env CNB_PLATFORM_API=0.15. Furthermore, newer stacks contain fewer pre-installed packages (for example,pythonis no longer included) and fewer default buildpacks (for example,cflinuxfs5does not contain the Go buildpack).Legacy stacks are still available but must be manually specified (via
kf push --stack cflinuxfs3 ...); otherwise,cflinuxfs4is used by default. We recommend manually specifying the legacy stack, updating to the latest KF release, and testing the application build and runtime in a separate space. Once verified, migrate away from the legacy stacks entirely.