Skip to content

Conversation

@testcara
Copy link
Member

As requested by the feature User access to artifacts built by Konflux, the UI now changes the default image repository visibility from public to private.
We need to update the visibility settings here accordingly.

@testcara testcara requested a review from a team as a code owner December 16, 2025 14:17
@snyk-io
Copy link

snyk-io bot commented Dec 16, 2025

Snyk checks have passed. No issues have been found so far.

Status Scanner Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues
Licenses 0 0 0 0 0 issues
Code Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@tisutisu
Copy link
Contributor

/retest


if imageRepository.Spec.Image.Visibility == "" {
imageRepository.Spec.Image.Visibility = imagerepositoryv1alpha1.ImageVisibilityPublic
imageRepository.Spec.Image.Visibility = imagerepositoryv1alpha1.ImageVisibilityPrivate
Copy link
Member

Choose a reason for hiding this comment

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

I'm not sure about the change.
Having all images private by default requires a paid plan on quay, which makes defaults not usable in upstream Konflux. So admins would have to pay for a quay plan or specify public visibility for every image, which is not a user friendly approach.

I suggest to have it configurable via an env var. If the env var is not set, it means public (to not to break current behavior).

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