mbalassi commented on code in PR #155:
URL:
https://github.com/apache/flink-kubernetes-operator/pull/155#discussion_r843292106
##########
docs/content/docs/operations/helm.md:
##########
@@ -109,3 +109,24 @@ spec:
skipCrds: true
...
```
+
+## Advanced customization techniques
+The Helm chart does not aim to provide configuration options for all the
possible deployment scenarios of the Operator. There are use cases for
injecting common tools and/or sidecars in most enterprise environments that
simply cannot be covered by public Helm charts.
+
+Fortunately, [post
rendering](https://helm.sh/docs/topics/advanced/#post-rendering) in Helm gives
you the ability to manually manipulate manifests before they are installed on a
Kubernetes cluster. This allows users to use tools like
[kustomize](https://kustomize.io) to apply configuration changes without the
need to fork public charts.
+
+The GitHub repository for the Operator contains a simple
[example](https://github.com/apache/flink-kubernetes-operator/tree/main/examples/kustomize)
on how to augment the Operator Deployment with an init container using
`kustomize`.
+
+```yaml
+initContainers:
+ - name: busybox
+ image: busybox:latest
+ command: [ 'sh','-c','echo Happy Customization!' ]```
+```
+
+You can enable the example using the `--post-renderer` option when installing
the Operator with Helm:
+
+```yaml
Review Comment:
nit: shell
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
