@@ -134,7 +134,7 @@ Template: corev1.PodTemplateSpec{
134
134
<h1 > Example(s) </h1 >
135
135
136
136
You can look for some code examples by checking the code which is generated via the Deploy
137
- Image plugin. ([ More info] ( ../plugins/deploy-image-plugin-v1-alpha.md ) )
137
+ Image plugin. ([ More info] ( ../plugins/available/ deploy-image-plugin-v1-alpha.md ) )
138
138
139
139
</aside >
140
140
@@ -154,32 +154,31 @@ support as recommended above, and that you properly configure the [nodeAffinity]
154
154
Therefore, ensure that you uncomment the following code in the ` config/manager/manager.yaml ` file
155
155
156
156
``` yaml
157
- # TODO(user): Uncomment the following code to configure the nodeAffinity expression
158
- # according to the platforms which are supported by your solution.
159
- # It is considered best practice to support multiple architectures. You can
160
- # build your manager image using the makefile target docker-buildx.
161
- # affinity:
162
- # nodeAffinity:
163
- # requiredDuringSchedulingIgnoredDuringExecution:
164
- # nodeSelectorTerms:
165
- # - matchExpressions:
166
- # - key: kubernetes.io/arch
167
- # operator: In
168
- # values:
169
- # - amd64
170
- # - arm64
171
- # - ppc64le
172
- # - s390x
173
- # - key: kubernetes.io/os
174
- # operator: In
175
- # values:
176
- # - linux
157
+ # TODO(user): Uncomment the following code to configure the nodeAffinity expression
158
+ # according to the platforms which are supported by your solution.
159
+ # It is considered best practice to support multiple architectures. You can
160
+ # build your manager image using the makefile target docker-buildx.
161
+ # affinity:
162
+ # nodeAffinity:
163
+ # requiredDuringSchedulingIgnoredDuringExecution:
164
+ # nodeSelectorTerms:
165
+ # - matchExpressions:
166
+ # - key: kubernetes.io/arch
167
+ # operator: In
168
+ # values:
169
+ # - amd64
170
+ # - arm64
171
+ # - ppc64le
172
+ # - s390x
173
+ # - key: kubernetes.io/os
174
+ # operator: In
175
+ # values:
176
+ # - linux
177
177
```
178
178
179
179
<aside class =" note " >
180
180
<h1 >Building images for releases</h1 >
181
181
182
-
183
182
You will probably want to automate the releases of your projects to ensure that the images are always built for the
184
183
same platforms. Note that Goreleaser also supports [ docker buildx] [ buildx ] . See its [ documentation] [ goreleaser-buildx ] for more detail.
185
184
@@ -221,4 +220,4 @@ end up labeled with ` kubernetes.io/os=linux`
221
220
[ node-affinity ] : https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#node-affinity
222
221
[ docker-manifest ] : https://docs.docker.com/engine/reference/commandline/manifest/
223
222
[ buildx ] : https://docs.docker.com/build/buildx/
224
- [ goreleaser-buildx ] : https://goreleaser.com/customization/docker/#use-a-specific-builder-with-docker-buildx
223
+ [ goreleaser-buildx ] : https://goreleaser.com/customization/docker/#use-a-specific-builder-with-docker-buildx
0 commit comments