Community Meeting August 10, 2023 about kcp HOT 7 CLOSED

Rebase 1.27 status

from kcp.

@sftim you had a topic when the last community meeting was canceled, do you want to discuss the topic on this meeting?

Image builds / releases

from kcp.

Topic: Update on kcp.io website theme (PR)

from kcp.

TMC - whats next ? API Naming, sharding, etc

from kcp.

Helm chart

from kcp.

@ rebase: volunteering for 1.28 rebase. I have a local branch with the rest of kubernetes/enhancements#4080. kcp is a good proof that 4080 is implemented well.

from kcp.

Meeting Notes

TMC - whats next ? API Naming, sharding, etc

• Repository has been open-sourced
• API group naming under kcp.io, move to tmc.kcp.io
• There are still open issues, contributions are very appreciated
• An extension to kcp, but currently a library plugged into the codebase
• TMC was in early stages of sharding support
• Tunneler no longer working, required some code in the core, should be possible though

Sharding Documentation (Intermission from previous topic)

• Sharding documentation needs to be created, it does not exist right now
• How should applications be built on top of kcp to be shard-aware?
• @MikeSpreitzer to create issue and assign it to @sttts

Rebase to 1.27

• Epic in #2986
• Not entirely clear what direction for the kubernetes/kubernetes fork to take
• Check in with folks in #kcp-dev about its status
• Potentially jump to 1.28 rebase immediately

Helm Chart

• Status: Supported as a way to install kcp, but can still be broken in the future as with kcp releases
• Issue with filesystem access in OpenShift
• "Developer" mode that makes it easy to try it out
• Sharding is not supported in the Helm Chart
• For the future: One shard is one Helm chart installation
• Making the kcp-front-proxy component optional is probably possible

from kcp.