Stop using gcr.io/kubebuilder/kube-rbac-proxy in TensorBoards before March 18, 2025

[thesuperzapper]

/kind bug

Currently the tensorboard controller makes use of the gcr.io/kubebuilder/kube-rbac-proxy image, which according to the Kubebuilder docs will become unavailable on or after March 18, 2025 (due to the deprecation of gcr.io)

The simlest fix will be to migrate directly to the replacement for gcr.io/kubebuilder/kube-rbac-proxy which is called brancz/kube-rbac-proxy who's image is hosted on quay.io/brancz/kube-rbac-proxy.

Alternatively we could use another method to remove gcr.io/kubebuilder/kube-rbac-proxy, see "How the metrics endpoint can be protected?" on this page:

• https://book.kubebuilder.io/reference/metrics

---

Related to: kserve/kserve#3734
Related to: kubeflow/pipelines#10891

[thesuperzapper]

@kimwnasptd we probably need to figure out the best solution here, as TensorBoards will stop working next year if we don't replace/remove this image.

[andreyvelich]

Thank you for creating this @thesuperzapper! Are we planning to keep TensorBoard in the next Kubeflow releases ?
According to your comment here: #7549 (comment), I though we will remove TensorBoard in Kubeflow 1.10