@@ -84,7 +84,7 @@ func InitFlags(fs *pflag.FlagSet) {
84
84
" Webhook Server port" )
85
85
86
86
fs.StringVar (&webhookCertDir, " webhook-cert-dir" , " /tmp/k8s-webhook-server/serving-certs/" ,
87
- " Webhook cert dir, only used when webhook-port is specified ." )
87
+ " Webhook cert dir." )
88
88
}
89
89
90
90
func main () {
@@ -279,7 +279,7 @@ well with practices like unit testing and generally makes the entire system more
279
279
280
280
### Error messages
281
281
282
- RuntimeExtension authors should be aware that error messages are surfaced as a conditions in Kubernetes resources
282
+ RuntimeExtension authors should be aware that error messages are surfaced as a conditions in Kubernetes resources
283
283
and recorded in Cluster API controller's logs. As a consequence:
284
284
285
285
- Error message must not contain any sensitive information.
@@ -291,16 +291,16 @@ and recorded in Cluster API controller's logs. As a consequence:
291
291
<h1 >Caution</h1 >
292
292
293
293
If an error message is not deterministic and it changes at every call even if the problem is the same, it could
294
- lead to to Kubernetes resources conditions continuously changing, and this generates a denial attack to
294
+ lead to to Kubernetes resources conditions continuously changing, and this generates a denial attack to
295
295
controllers processing those resource that might impact system stability.
296
296
297
297
</aside >
298
298
299
299
### ExtensionConfig
300
300
301
- To register your runtime extension apply the ExtensionConfig resource in the management cluster, including your CA
302
- certs, ClusterIP service associated with the app and namespace, and the target namespace for the given extension. Once
303
- created, the extension will detect the associated service and discover the associated Hooks. For clarification, you can
301
+ To register your runtime extension apply the ExtensionConfig resource in the management cluster, including your CA
302
+ certs, ClusterIP service associated with the app and namespace, and the target namespace for the given extension. Once
303
+ created, the extension will detect the associated service and discover the associated Hooks. For clarification, you can
304
304
check the status of the ExtensionConfig. Below is an example of ` ExtensionConfig ` -
305
305
306
306
``` yaml
@@ -328,7 +328,7 @@ spec:
328
328
329
329
Settings can be added to the ExtensionConfig object in the form of a map with string keys and values. These settings are
330
330
sent with each request to hooks registered by that ExtensionConfig. Extension developers can implement behavior in their
331
- extensions to alter behavior based on these settings. Settings should be well documented by extension developers so that
331
+ extensions to alter behavior based on these settings. Settings should be well documented by extension developers so that
332
332
ClusterClass authors can understand usage and expected behaviour.
333
333
334
334
Settings can be provided for individual external patches by providing them in the ClusterClass ` .spec.patches[*].external.settings`.
@@ -380,7 +380,7 @@ curl -X 'POST' 'http://127.0.0.1:8001/api/v1/namespaces/default/services/https:w
380
380
-d '{"apiVersion":"hooks.runtime.cluster.x-k8s.io/v1alpha1","kind":"DiscoveryRequest"}' | jq
381
381
` ` `
382
382
383
- For more details about the API of the Runtime Extensions please see <button onclick="openSwaggerUI()">Swagger UI</button>.
383
+ For more details about the API of the Runtime Extensions please see <button onclick="openSwaggerUI()">Swagger UI</button>.
384
384
For more details on proxy support please see [Proxies in Kubernetes](https://kubernetes.io/docs/concepts/cluster-administration/proxies/).
385
385
386
386
<script>
0 commit comments