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.

Sign up for GitHub

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

Jump to bottom

Any specific reason for Kube-rbac-proxy:v0.13.1 being referenced from an individual repo #1423

Closed
harshadsonde opened this issue Jan 19, 2023 · 1 comment · Fixed by #1429
Closed

Any specific reason for Kube-rbac-proxy:v0.13.1 being referenced from an individual repo #1423

harshadsonde opened this issue Jan 19, 2023 · 1 comment · Fixed by #1429
Assignees
@saschagrunert
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@harshadsonde
Copy link

What happened:
One of the environment package being used "kube-rbac-proxy" image is being taken from repo "quay.io/brancz/kube-rbac-proxy:v0.13.1"
Is there a specific reason that the image is being referenced from the above mentioned individual repo ? As we can see that similar image is also available at "gcr.io/kubebuilder/kube-rbac-proxy:v0.13.1" ?

What you expected to happen:
Can the image of kube-rbac-proxy be referenced from "gcr.io/kubebuilder/kube-rbac-proxy" instead of
"quay.io/brancz/kube-rbac-proxy:v0.13.1" repo ?

How to reproduce it (as minimally and precisely as possible):
The above repo link is referenced under deployment.yaml file.

Anything else we need to know?:
@harshadsonde harshadsonde added the kind/bug Categorizes issue or PR as related to a bug. label Jan 19, 2023
@saschagrunert
Copy link
Member

Hm we started to use kube-rbac-proxy with version v0.9.0 and maybe they switcher later on to the kubebuilder org. We should definitely fix that. Do you mind opening a PR for that @harshadsonde?

saschagrunert added a commit to saschagrunert/security-profiles-operator that referenced this issue Jan 23, 2023
@saschagrunert
Switch to gcr.io/kubebuilder/kube-rbac-proxy
31bdbb1 
The old location does not seem to be the official one, so we switch over
to the new one as well as adapt the dependency verification.

Fixes kubernetes-sigs#1423

Signed-off-by: Sascha Grunert <sgrunert@redhat.com>
@saschagrunert saschagrunert mentioned this issue Jan 23, 2023
Merged
@saschagrunert saschagrunert self-assigned this Jan 23, 2023
saschagrunert added a commit to saschagrunert/security-profiles-operator that referenced this issue Jan 24, 2023
@saschagrunert
Switch to gcr.io/kubebuilder/kube-rbac-proxy
0415f50 
The old location does not seem to be the official one, so we switch over
to the new one as well as adapt the dependency verification.

Fixes kubernetes-sigs#1423

Signed-off-by: Sascha Grunert <sgrunert@redhat.com>
saschagrunert added a commit to saschagrunert/security-profiles-operator that referenced this issue Jan 24, 2023
@saschagrunert
Switch to gcr.io/kubebuilder/kube-rbac-proxy
b3e8b74 
The old location does not seem to be the official one, so we switch over
to the new one as well as adapt the dependency verification.

Fixes kubernetes-sigs#1423

Signed-off-by: Sascha Grunert <sgrunert@redhat.com>
k8s-ci-robot pushed a commit that referenced this issue Jan 24, 2023
@saschagrunert @k8s-ci-robot
Switch to gcr.io/kubebuilder/kube-rbac-proxy
d2fcaf9 
The old location does not seem to be the official one, so we switch over
to the new one as well as adapt the dependency verification.

Fixes #1423

Signed-off-by: Sascha Grunert <sgrunert@redhat.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@saschagrunert saschagrunert

Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Switch to gcr.io/kubebuilder/kube-rbac-proxy saschagrunert/security-profiles-operator
2 participants
@harshadsonde @saschagrunert