✨ (kubebuilder) new config image job for kube-rbac-proxy image

[camilamacedo86]

Description

Creating a job to trigger the build of the image gcr.io/kubebuilder/kube-rbac-proxy in the new registry.
More info: kubernetes-sigs/kubebuilder#3362

Motivation: kubernetes-sigs/kubebuilder#3230

Closes: https://github.com/kubernetes/test-infra/pull/28803/files

[camilamacedo86]

/assign @rikatz

@rikatz could you please give a hand here and let us know if this one is correct?

c/c @yashsingh74 @varshaprasad96

[rikatz]

suggestion: instead of using --gcb-config here, probably you want to create a new directory in https://github.com/kubernetes-sigs/kubebuilder/tree/kube-rbac-proxy-releases with a proper cloudbuild, and point to that directory

eg.:

args:
....
  - images/

And add a new cloudbuild.yaml inside this directory (see https://github.com/kubernetes/ingress-nginx/blob/main/cloudbuild.yaml). In this case if you want to test different combinations of cloudbuild.yaml later you won't need to change the one that is already working.

[rikatz]

ok I see it here: https://github.com/kubernetes-sigs/kubebuilder/pull/3362/files

let me continue the discussion there

[camilamacedo86]

So, I understand that is right. Am I right?

See that I am doing like : https://github.com/kubernetes/test-infra/blob/3b85f96f30d6f1ce48639ccbdbde396cc3c8b183/config/jobs/image-pushing/k8s-staging-kustomize.yaml#LL28C1-L38C18

Note that for Kubebuilder, we do not use docker to build the image.

So, I understand that when we merge this one, we should see a new trigger created in the GCP, such as we have now:

[BenTheElder]

+1 for this suggestion, but not blocking
put a hold in case

[camilamacedo86]

Hi @rikatz,

I did the changes could we get this one merged, and then we try it out to see if it will work?

[BenTheElder]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: BenTheElder, camilamacedo86

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• config/jobs/image-pushing/OWNERS [BenTheElder]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[BenTheElder]

/hold

[camilamacedo86]

/hold cancel

[k8s-ci-robot]

@camilamacedo86: Updated the job-config configmap in namespace default at cluster test-infra-trusted using the following files:

• key k8s-staging-kubebuilder.yaml using file config/jobs/image-pushing/k8s-staging-kubebuilder.yaml

In response to this:

Description

Creating a job to trigger the build of the image gcr.io/kubebuilder/kube-rbac-proxy in the new registry.
More info: kubernetes-sigs/kubebuilder#3362

Motivation: kubernetes-sigs/kubebuilder#3230

Closes: https://github.com/kubernetes/test-infra/pull/28803/files

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.