- Name: 2023H2 Roadmap
- Start Date: 2023-06-07
- Author(s): hone
- Status: Draft
- RFC Pull Request: (leave blank)
- CNB Pull Request: (leave blank)
- CNB Issue: (leave blank)
- Supersedes: (put "N/A" unless this replaces an existing RFC, then link to that RFC)
This RFC details the second half of the 2023 Roadmap leading up to KubeCon NA.
- Finished - The item has already been completed and there is no need to put it on the current roadmap.
- Continue - More work is needed and it will be continued as part of the current roadmap.
- Defer - This item will be parked for now and doesn't make the cut for the current roadmap.
With KubeCon NA coming up around the corner, it's time to plan out what we want to achieve as a project. It's also an opportunity to review items from the H1 roadmap.
This roadmap is going to be split into two sections covering the first the H1 Roadmap and status, as well as new items we want to tackle leading up to KubeCon NA.
As a project, we've made good progress on our H1 roadmap, but still need some more time to get some of them across the finish line.
- Owner: @natalieparellano
- Status: Continue
- Links: RFC
This is close and will be released as part of Platform 0.12
, Buildpack 0.10
, lifecycle 0.17.0
, and pack 0.30.0
.
- Owner: @jkutner
- Status: Continue
- Links: RFC
This is close and will be released as part of Platform 0.12
, Buildpack 0.10
, lifecycle 0.17.0
, and pack 0.30.0
.
- Owner: @hone
- Status: Continue
- Links: RFC
The RFC is written, but feedback needs to be incoporated before re-opening for review.
- Owner: @samj1912
- Status: Finished
- Links: Buildpacks Community Organization RFC
The RFC has been merged and the buildpacks community GitHub org have been created.
- Owner: @dfreilich
- Status: Defer
- Links: Pack Pull Request
This item has been deferred for now, but we will work with anyone who wants to push this forward.
- Owner: @microwavables (Team Lead sponsor @jkutner)
- Links: VMware Tanzu Community Engagement Health Checks
The project is lucky to have a Community Manager! This is one of the projects proposed by @microwavables to set a base line to measure how we're doing as a community.
- Owner: @joshwlewis (Team Lead sponsor @hone)
- Links: TBD
Currently, Buildpack Authors have little to no tools around visibility with their buildpacks as they run on a platform, including pack
. In some of the Heroku v2 buildpacks, they implemented logging that could be handed off to the platform by running bin/report
. This work stream is about standardizing output for both successful AND failed builds that Buildpack Authors can use to instrument their buildpack.
- Owner: @jabrown85
- Links: RFC
A platform operator can configure registry mirrors that lifecycle could use without needing for the manifest to have to point to it. This will allow a platform to reduce the risk of service operations from external registry sources and reduce public network bandwidth usage. The resulting image when taken off platform will also function without needing access to the registry mirror.
- Owner: @jjbustamante (Team Lead sponsor @hone)
- Links: RFC
kpack
is being proposed to be donated as an open source project in the Cloud Native Buildpacks' new Community Organization as a vendor neutral staging ground. This will give the project space to grow the project contributor base from multiple vendors. While work has started on this in H1, this item represents our commitment as a project to see this through and set this project up for success under the CNB governance umbrella.
- Owner: @natalieparellano
- Links: Cosign Integration RFC, SBOM layer RFC,
While CNBs support SBOMs today, they were designed a few years ago and tooling around them have been evolving. This work stream is about making CNBs integrate better with tools like cosign's SBOM spec and the upcoming OCI References feature in OCI Image Manifest 1.1.
- Owner: @jjbustamante
- Links: RFC
Multi-arch support has been a highly request feature with the growing popularity of the ARM architecture. In order to better support this with Buildpacks, the first step will be to able to use manifest lists to provide a single URI for Buildpacks that support multiple architectures.
See What it is for the details. We'll be following the same process from the 2023H1 Roadmap RFC if approved.
N/A
- Agreeing to more work, while we still need to finish 2023H1 items.
- Do Nothing and just hunker down on our existing items.
See Prior Art from 2023H1 Roadmap RFC.
- What parts of the design do you expect to be resolved before this gets merged?
- What parts of the design do you expect to be resolved through implementation of the feature?
- What related issues do you consider out of scope for this RFC that could be addressed in the future independently of the solution that comes out of this RFC?
N/A