Skip to content
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

kpack compatible k3d cluster setup #557

Open
wants to merge 1 commit into
base: kpack-resources
Choose a base branch
from

Conversation

sgaist
Copy link
Collaborator

@sgaist sgaist commented Nov 29, 2024

Describe your changes

This PR adds a script that allows to setup a k3d cluster in such a way that kpack can use it.

A k3d registry is created externally so it can be re-used if the cluster must be re-created without incurring the time required to populate it.

The image required for the builder is copied to the registry using a Kubernetes job.

@sgaist sgaist requested a review from a team as a code owner November 29, 2024 16:25
@Panaetius Panaetius force-pushed the kpack-resources branch 2 times, most recently from 4a1af72 to 8234729 Compare December 2, 2024 08:32
@Panaetius Panaetius force-pushed the sgaist/kpack-resources branch 2 times, most recently from ca32bfa to 3d31917 Compare December 2, 2024 08:37
@Panaetius Panaetius force-pushed the kpack-resources branch 2 times, most recently from 46ebfeb to 41b31b9 Compare December 2, 2024 08:51
@Panaetius Panaetius force-pushed the sgaist/kpack-resources branch 2 times, most recently from 7634433 to 980c77a Compare December 2, 2024 09:01
The setup creates an independent k3d registry that can be
reused and configures the k3d cluster to be able to access
it.

The registry thus survives cluster deletion and this will
speed up cluster recreation.

kpack can access it through http.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant