-
Notifications
You must be signed in to change notification settings - Fork 170
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
shellcheck image is hosted in a VMware-owned registry #827
Labels
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
Comments
/assign |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
k8s-ci-robot
added
the
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
label
May 30, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
Hey folks,
just wanted to let you know that the shellcheck image used (gcr.io/cluster-api-provider-vsphere/extra/shellcheck) is hosted in a VMware-owned registry (/ GCP project). In CAPV we replaced usage of the image through a script (https://github.com/kubernetes-sigs/cluster-api-provider-vsphere/blob/main/hack/verify-shellcheck.sh). I would highly recommend also migrating to the script.
We won't delete the image from the current registry, but we also cannot guarantee that it will exist forever there.
The text was updated successfully, but these errors were encountered: