1
1
# cloud-provider-gcp
2
2
3
+ This repository holds the code for gcp-controller-manager as well as cloud-controller-manager
4
+
3
5
## Publishing gcp-controller-manager image
4
6
5
- This command will build and publish
7
+ This command will build and publish gcp-controller-manager
6
8
` gcr.io/k8s-image-staging/gcp-controller-manager:latest ` :
7
9
8
10
```
@@ -20,6 +22,26 @@ This command will build and publish
20
22
IMAGE_REGISTRY=example.com IMAGE_REPO=my-repo IMAGE_TAG=v1 bazel run //cmd/gcp-controller-manager:publish
21
23
```
22
24
25
+ ## Publishing cloud-controller-maanger image
26
+
27
+ This command will build and publish cloud-controller-manager
28
+ ` gcr.io/k8s-image-staging/cloud-controller-manager:latest ` :
29
+
30
+ ```
31
+ bazel run //cmd/cloud-controller-manager:publish
32
+ ```
33
+
34
+ Environment variables ` IMAGE_REGISTRY ` , ` IMAGE_REPO ` and ` IMAGE_TAG ` can be
35
+ used to override destination GCR repository and tag.
36
+
37
+ This command will build and publish
38
+ ` example.com/my-repo/gcp-controller-manager:v1 ` :
39
+
40
+
41
+ ```
42
+ IMAGE_REGISTRY=example.com IMAGE_REPO=my-repo IMAGE_TAG=v1 bazel run //cmd/cloud-controller-manager:publish
43
+ ```
44
+
23
45
# Cross-compiling
24
46
25
47
Selecting the target platform is done with the ` --platforms ` option with ` bazel ` .
@@ -87,3 +109,16 @@ To re-generate `BUILD` files:
87
109
``` sh
88
110
tools/update_bazel.sh
89
111
```
112
+
113
+ # Tagging for new cloud-controller-manager versions
114
+
115
+ To trigger a new image for cloud-controller-manager, you need to add a git tag.
116
+ This needs to have the format ` ccm/vX.Y.Z ` . For example.
117
+
118
+ ```
119
+ git tag -a ccm/v27.1.0 -m "CCM build for Kubernetes v1.27.1"
120
+ ```
121
+
122
+ The major version X corresponds to the Kubernetes minor version. The minor
123
+ version Y corresponds to the Kubernetes patch version and the patch version Z
124
+ corresponds to the CCM patch version.
0 commit comments