Skip to content

feat(builds): add the possibility to configure insecure registries#4438

Open
sgaist wants to merge 3 commits into
masterfrom
feat/support-insecure-registries-for-builds
Open

feat(builds): add the possibility to configure insecure registries#4438
sgaist wants to merge 3 commits into
masterfrom
feat/support-insecure-registries-for-builds

Conversation

@sgaist

@sgaist sgaist commented Apr 16, 2026

Copy link
Copy Markdown
Collaborator

Describe your changes

This PR adds the possbility to configure insecure registries to be used when building images.

This can be used, for example, with registries such has Harbor, behind a self-signed certificate in a development setup.

Links and tickets

Related to SwissDataScienceCenter/renku-data-services#1264

@sgaist sgaist requested a review from a team as a code owner April 16, 2026 15:00
@sgaist sgaist requested review from SalimKayal, leafty and olevski April 16, 2026 15:01

@leafty leafty left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The PR contents do not correspond to the PR description and title.

@sgaist sgaist force-pushed the feat/support-insecure-registries-for-builds branch from 3f5b90a to 4e1b94a Compare April 17, 2026 07:03
@sgaist sgaist changed the base branch from master to release-2.17.0 April 17, 2026 07:03
@sgaist sgaist requested a review from leafty April 17, 2026 07:04
@sgaist

sgaist commented Apr 17, 2026

Copy link
Copy Markdown
Collaborator Author

@leafty all good now

I have mixed something somewhere between branch updates, cherry-pick and stash...

@leafty leafty left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Comment thread helm-chart/renku/values.yaml
Co-authored-by: Flora Thiebaut <flora.thiebaut@sdsc.ethz.ch>
leafty
leafty previously approved these changes Apr 17, 2026
@leafty leafty changed the base branch from release-2.17.0 to release-2.18.0 May 7, 2026 09:51
@olevski

olevski commented Jun 24, 2026

Copy link
Copy Markdown
Member

Lets bump this to 2.19.0. Sorry @sgaist. But we will also tag 2.19.0 relatively quickly because there are still some features from the latest build that did not get merged.

@sgaist

sgaist commented Jun 24, 2026

Copy link
Copy Markdown
Collaborator Author

Lets bump this to 2.19.0. Sorry @sgaist. But we will also tag 2.19.0 relatively quickly because there are still some features from the latest build that did not get merged.

No problem, there's SwissDataScienceCenter/renku-data-services#1359 that should get addressed first and then this one updated accordingly.

Base automatically changed from release-2.18.0 to master June 27, 2026 17:12
@olevski olevski dismissed leafty’s stale review June 27, 2026 17:12

The base branch was changed.

@olevski

olevski commented Jun 27, 2026

Copy link
Copy Markdown
Member

Please target release-2.19.0

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.

4 participants