K8s.gcr.io Redirect to registry.k8s.io - ¿does it affect k6-operator?

Grafana k6 k6-operator
1

Hi guys,
Based on this official statement which change to do is around the corner (April 4 2023) I wonder if the k6-operator deployment will be affected, if so, I’d like to ask the k6-operator team if it’s necessary to replace the lines of “image” and to point to " registry.k8s.io"

kind: Deployment
metadata:
  labels:
    control-plane: controller-manager
  name: k6-operator-controller-manager
  namespace: k6-operator-system
spec:
  replicas: 1
  selector:
    matchLabels:
      control-plane: controller-manager
  template:
    metadata:
      labels:
        control-plane: controller-manager
    spec:
      containers:
      - args:
        - --secure-listen-address=0.0.0.0:8443
        - --upstream=http://127.0.0.1:8080/
        - --logtostderr=true
        - --v=10
        **image: gcr.io/kubebuilder/kube-rbac-proxy:v0.5.0**
        name: kube-rbac-proxy
        ports:
        - containerPort: 8443
          name: https
      - args:
        - --metrics-addr=127.0.0.1:8080
        - --enable-leader-election
        command:
        - /manager
        **image: ghcr.io/k6io/operator:latest**
        name: manager
        resources:
          limits:
            cpu: 100m
            memory: 100Mi
          requests:
            cpu: 100m
            memory: 50Mi
      serviceAccount: k6-operator-controller
      terminationGracePeriodSeconds: 10

thanks!

3

Hi @cesarcorrea!
Thanks for pinging us about this one. I’ve looked into that announcement a couple of weeks ago and it didn’t seem like it should affect us. So we have kube-rbac-proxy that you pointed out but it is built by kubebuilder project putting images here. Note that their URL is under gcr.io and not k8s.gcr.io. And there are no issues opened in kubebuilder about migration of images. I assume that this announcement is about “core” registry only, i.e. images like apiserver, etcd, etc. but k6 Operator doesn’t use those directly.

Let me know if you have other info on this!

2 Likes
4

I just wanted to mention that you should change “k6io” with “grafana” for the image name. Either works for now, but “grafana” is the correct one.

5

got it Paul, so, you mean some like :

image: ghcr.io/grafana/operator:latest
6

Correct. We’re still publishing to both locations, but the k6io will probably stop someday.