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
These instructions install _kube-fledged_ to a separate namespace called "kube-fledged", using Helm operator and pre-built images in [Docker Hub.](https://hub.docker.com/u/senthilrch)
@@ -127,6 +139,12 @@ These instructions install _kube-fledged_ to a separate namespace called "kube-f
127
139
$ kubectl get imagecaches -n kube-fledged (Output should be: 'No resources found')
128
140
```
129
141
142
+
- Optional: Deploy _kube-fledged webhook server_ to the cluster. This component enables validating the ImageCache CR.
143
+
144
+
```
145
+
$ make deploy-webhook-server-using-operator
146
+
```
147
+
130
148
## Helm chart parameters
131
149
132
150
Parameters of the helm chart are documented [here](docs/helm-parameters.md)
@@ -277,9 +295,18 @@ Run the following command to remove _kube-fledged_ from the cluster.
277
295
278
296
```
279
297
$ make remove-kubefledged (if you deployed using YAML manifests)
298
+
$ helm delete kube-fledged -n ${KUBEFLEDGED_NAMESPACE} (if you deployed using Helm chart)
280
299
$ make remove-operator-and-kubefledged (if you deployed using Helm Operator)
281
300
```
282
301
302
+
Note: To remove the _kube-fledged webhook server_ alone.
303
+
304
+
```
305
+
$ make remove-webhook-server (if you deployed using YAML manifests)
306
+
$ helm upgrade kube-fledged deploy/kubefledged-operator/helm-charts/kubefledged -n ${KUBEFLEDGED_NAMESPACE} --set webhookServer.enable=false --wait --debug (if you deployed using Helm chart)
307
+
$ make remove-webhook-server-using-operator (if you deployed using Helm Operator)
308
+
```
309
+
283
310
## How it works
284
311
285
312
Kubernetes allows developers to extend the kubernetes api via [Custom Resources](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/). _kube-fledged_ defines a custom resource of kind “ImageCache” and implements a custom controller (named _kubefledged-controller_). _kubefledged-controller_ does the heavy-lifting for managing image cache. Users can use kubectl commands for creation and deletion of ImageCache resources.
@@ -297,6 +324,8 @@ For more detailed description, go through _kube-fledged's_ [design proposal](doc
297
324
298
325
`--image-pull-policy:` Image pull policy for pulling images into and refreshing the cache. Possible values are 'IfNotPresent' and 'Always'. Default value is 'IfNotPresent'. Image with no or ":latest" tag are always pulled.
299
326
327
+
`--service-account-name:` serviceAccountName used in Jobs created for pulling or deleting images. Optional flag. If not specified the default service account of the namespace is used
328
+
300
329
`--stderrthreshold:` Log level. set the value of this flag to INFO
flag.StringVar(&serviceAccountName, "service-account-name", "", "serviceAccountName used in Jobs created for pulling/deleting images. Optional flag. If not specified the default service account of the namespace is used")
0 commit comments