You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The releases occur in an account in the Google Cloud (See [here](https://console.cloud.google.com/cloud-build/builds?project=kubebuilder)) using Cloud Build.
27
+
28
+
### To build the Kubebuilder CLI binaries:
29
+
30
+
A trigger `build-kb-release` is configured to call [build/cloudbuild.yaml](build/cloudbuild.yaml).
31
+
This trigger will be executed when any new tag be published.
32
+
The tags must be built from the release branch (Currently, `release-3`).
33
+
34
+
Also, we have a trigger to generate snapshots builds from the master branch.
35
+
This trigger will call [build/cloudbuild_snapshot.yaml](build/cloudbuild_snapshot.yaml)
36
+
when any change needs to be performed on master.
37
+
38
+
### To build the Kubebuilder-tools: (Artifacts required to use ENV TEST)
39
+
40
+
Kubebuilder projects requires artifacts which are used to do test with ENV TEST (when we call `make test` target)
41
+
These artifacts can be checked in the service page: https://storage.googleapis.com/kubebuilder-tools
42
+
43
+
The build is made from the branch [tools-releases](https://github.com/kubernetes-sigs/kubebuilder/tree/tools-releases) and the trigger will call the `build/cloudbuild_tools.yaml` passing
44
+
as argument the architecture and the SO that should be used, e.g:
45
+
46
+
<imgwidth="553"alt="Screenshot 2022-04-30 at 10 15 41"src="https://user-images.githubusercontent.com/7708031/166099666-ae9cd2df-73fe-47f6-a987-464f63df9a19.png">
47
+
48
+
For further information see the [README](https://github.com/kubernetes-sigs/kubebuilder/blob/tools-releases/README.md).
49
+
50
+
### To build the `kube-rbac-proxy` images:
51
+
52
+
These images are built from the project [brancz/kube-rbac-proxy](https://github.com/brancz/kube-rbac-proxy).
53
+
The projects built with Kubebuilder creates a side container with `kube-rbac-proxy` to protect the Manager.
54
+
55
+
These images are can be checked in the consolse, see [here](https://console.cloud.google.com/gcr/images/kubebuilder/GLOBAL/kube-rbac-proxy).
56
+
57
+
The project `kube-rbac-proxy` is in the process to be donated to the k8s org. However, it is going on for a long time and then,
58
+
we have no ETA for that to occur. When that occurs we can automate this process. But until there we need to generate these images
59
+
by bumping the versions/tags released by `kube-rbac-proxy` on the branch
then the `build/cloudbuild_kube-rbac-proxy.yaml` will generate the images.
62
+
63
+
To check an example, see the pull request [#2578](https://github.com/kubernetes-sigs/kubebuilder/pull/2578).
64
+
65
+
**Note**: we cannot use the images produced by the project `kube-rbac-proxy` because we need to ensure
66
+
to Kubebuilder users that these images will be available.
67
+
68
+
### To build the `gcr.io/kubebuilder/pr-verifier` images:
69
+
70
+
These images are used to verify the PR title and description. They are built from [kubernetes-sigs/kubebuilder-release-tools](https://github.com/kubernetes-sigs/kubebuilder-release-tools/).
71
+
In Kubebuilder, we have been using this project via the GitHub action [.github/workflows/verify.yml](.github/workflows/verify.yml)
0 commit comments