From 96774ca9201241f7f5b56caa25f403fe4a9557a9 Mon Sep 17 00:00:00 2001 From: Camila Macedo <7708031+camilamacedo86@users.noreply.github.com> Date: Tue, 19 Nov 2024 03:14:01 +0000 Subject: [PATCH 1/2] Update roadmap_2024.md - Latest Status - Nov 2024 --- roadmap/roadmap_2024.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roadmap/roadmap_2024.md b/roadmap/roadmap_2024.md index d07b22769a5..dbb77d3efdb 100644 --- a/roadmap/roadmap_2024.md +++ b/roadmap/roadmap_2024.md @@ -77,7 +77,7 @@ to refine these proposals. Your involvement is crucial in shaping the future of --- ### Proposal Pending: Seeking Feedbacks for kube-rbac-proxy's Role in Default Scaffold -**Status:** :white_check_mark: Complete but :raised_hands: Seek Contributors and help with the next steps, see: https://github.com/kubernetes-sigs/kubebuilder/issues/3871 +**Status:** :white_check_mark: Complete - **Resolution**: The usage of kube-rbac-proxy has been discontinued from the default scaffold. We plan to provide other helpers to protect the metrics endpoint. Furthermore, once the project is accepted under kubernetes-sig or kubernetes-auth, we may contribute to its maintainer in developing an external plugin for use with projects built with Kubebuilder. - **Proposal**: [https://github.com/kubernetes-sigs/kubebuilder/blob/master/designs/discontinue_usage_of_kube_rbac_proxy.md](https://github.com/kubernetes-sigs/kubebuilder/blob/master/designs/discontinue_usage_of_kube_rbac_proxy.md) From 1cfdc804e706e6a57bf61f462666a39d2572fd4a Mon Sep 17 00:00:00 2001 From: Camila Macedo <7708031+camilamacedo86@users.noreply.github.com> Date: Tue, 19 Nov 2024 03:16:37 +0000 Subject: [PATCH 2/2] Update roadmap_2024.md --- roadmap/roadmap_2024.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/roadmap/roadmap_2024.md b/roadmap/roadmap_2024.md index dbb77d3efdb..9e8bac4d4c0 100644 --- a/roadmap/roadmap_2024.md +++ b/roadmap/roadmap_2024.md @@ -30,13 +30,13 @@ see [GitHub Pull Request #3632](https://github.com/kubernetes-sigs/kubebuilder/p **Motivation:** The growth of the Kubernetes ecosystem underscores the need for flexible and accessible distribution methods. A Helm chart packaging plugin would simplify the distribution of the solutions -and allow easily integrations with common applications used by administrators. +and allow easy integrations with common applications used by administrators. --- ### Transition from Google Cloud Platform (GCP) to build and promote binaries and images **Status:** -- **Kubebuilder CLI**: :white_check_mark: Complete. It has been building using go releaser. [More info](./../build/.goreleaser.yml) +- **Kubebuilder CLI**: :white_check_mark: Complete. It has been built using Go releaser. [More info](./../build/.goreleaser.yml) - **kube-rbac-proxy Images:** :white_check_mark: Complete. ([More info](https://github.com/kubernetes-sigs/kubebuilder/discussions/3907)) - **EnvTest binaries:** :white_check_mark: Complete Controller-Runtime maintainers are working in a solution to build them out and take the ownership over this one. More info: - https://kubernetes.slack.com/archives/C02MRBMN00Z/p1712457941924299 @@ -46,11 +46,11 @@ and allow easily integrations with common applications used by administrators. - **PR Check image:** 🙌 Seeking Contributions to do the required changes - See that the images used to check the PR titles are also build and promoted by the Kubebuilder project in GCP but are from the project: https://github.com/kubernetes-sigs/kubebuilder-release-tools. The plan in this case is to use the e2e shared infrastructure. [More info](https://github.com/kubernetes/k8s.io/issues/2647#issuecomment-2111182864) **Objective:** Shift Kubernetes (k8s) project infrastructure from GCP to shared infrastructures. -Furthermore, move away from the registry `k8s.gcr.io` to `registry.k8s.io`. +Furthermore, move from the registry `k8s.gcr.io` to `registry.k8s.io`. **Motivation:** The initiative to move away from GCP aligns with the broader k8s project's -goal of utilizing shared infrastructures. This transition is crucial for ensure the availability -of the artifacts in the long run and align complience with other projects under the kubernetes-sig org. +goal of utilizing shared infrastructures. This transition is crucial for ensuring the availability +of the artifacts in the long run and aligning compliance with other projects under the kubernetes-sig org. [Issue #2647](https://github.com/kubernetes/k8s.io/issues/2647) provides more details on the move. **Context:** Currently, Google Cloud is used only for: @@ -75,7 +75,7 @@ available [here](https://github.com/kubernetes-sigs/kubebuilder/blob/master/RELE to refine these proposals. Your involvement is crucial in shaping the future of secure and efficient project scaffolding in Kubebuilder.** --- -### Proposal Pending: Seeking Feedbacks for kube-rbac-proxy's Role in Default Scaffold +### kube-rbac-proxy's Role in Default Scaffold **Status:** :white_check_mark: Complete