-
**What happened?**
I'm trying to use a private registry in GCR, and runs my workspace on Minikube.
I already authenticated on Minikube (by addon gcp-auth) and on docker, with docker login, but when t…
-
We're using gcr.io based Prow images in project-infra. k8s stopped publishing images 2 months ago, hence we're not getting autobumper to bump new images anymore.
Ref: https://github.com/metal3-io/p…
-
**Describe the bug**
I've setup argocd image updater in my GKE autopilot cluster using helm charts. It works well with the config below:
```
argocd-image-updater:
serviceAccount:
name: ar…
-
Deadline October for our projects.
-
{
"platform":"",
"hub-mirror": [
"gcr.io/k8s-minikube/kicbase:v0.0.45"
]
}
-
{
"platform":"",
"hub-mirror": [
"gcr.io/knative-releases/knative.dev/serving/cmd/queue"
]
}
-
{
"platform":"",
"hub-mirror": [
"gcr.io/knative-releases/knative.dev/serving/cmd/webhook"
]
}
-
{
"platform":"",
"hub-mirror": [
"gcr.io/knative-releases/knative.dev/serving/cmd/webhook"
]
}
-
**Expected behavior and actual behavior:**
When a pull is done over a pull-through cache repository using GHCR and GCR, the image should be stored in the cache together with their tags. However, the …
-
#### What would you like to be added:
Part of:
- https://github.com/kubernetes/k8s.io/issues/1343
Migrate exiting GCR container registries used for the release process to GCP Artifact reg…