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

feat: custom environment build #541

Draft
wants to merge 6 commits into
base: main
Choose a base branch
from
Draft

feat: custom environment build #541

wants to merge 6 commits into from

Conversation

Panaetius
Copy link
Member

No description provided.

@Panaetius Panaetius force-pushed the kpack-resources branch 2 times, most recently from 7d0dacf to 29577cd Compare November 25, 2024 10:49
@Panaetius Panaetius force-pushed the kpack-resources branch 5 times, most recently from 5f3ddf5 to 46ebfeb Compare December 2, 2024 08:40
@coveralls
Copy link

coveralls commented Dec 2, 2024

Pull Request Test Coverage Report for Build 12256793455

Details

  • 14 of 16 (87.5%) changed or added relevant lines in 3 files are covered.
  • 6 unchanged lines in 3 files lost coverage.
  • Overall coverage increased (+0.001%) to 85.742%

Changes Missing Coverage Covered Lines Changed/Added Lines %
components/renku_data_services/notebooks/api/classes/k8s_client.py 4 6 66.67%
Files with Coverage Reduction New Missed Lines %
components/renku_data_services/base_api/auth.py 1 83.13%
components/renku_data_services/crc/db.py 1 85.68%
components/renku_data_services/crc/blueprints.py 4 93.06%
Totals Coverage Status
Change from base Build 12255615064: 0.001%
Covered Lines: 14529
Relevant Lines: 16945

💛 - Coveralls

@Panaetius Panaetius force-pushed the kpack-resources branch 3 times, most recently from 7a754c1 to 8665a14 Compare December 2, 2024 09:22
@Panaetius Panaetius force-pushed the kpack-resources branch 2 times, most recently from 0b5ffb5 to d9edcaf Compare December 10, 2024 13:02
@Panaetius Panaetius changed the title feat: add kpack k8s resources feat: custom environment build Dec 18, 2024
* refactor: implement k3d cluster creation working with kpack and Shipwright

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 and Shipwrite can access it through http.

The script can install either or both solutions.

The Makefile installs Shipwright be default
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.

3 participants