You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Gyula Fora (Jira)" <ji...@apache.org> on 2022/10/31 08:06:00 UTC

[jira] [Closed] (FLINK-29799) How to override ConfigMap values while deploying the Operator via OLM?

     [ https://issues.apache.org/jira/browse/FLINK-29799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gyula Fora closed FLINK-29799.
------------------------------
    Resolution: Won't Do

The OLM installation is currently not supported by the community. You can ask on the user mailing list / slack you might be able to find some help.

> How to override ConfigMap values while deploying the Operator via OLM?
> ----------------------------------------------------------------------
>
>                 Key: FLINK-29799
>                 URL: https://issues.apache.org/jira/browse/FLINK-29799
>             Project: Flink
>          Issue Type: Improvement
>          Components: Kubernetes Operator
>            Reporter: Cansu Kavili
>            Priority: Not a Priority
>
> Hi,
> Flink Kubernetes Operator is great - thank you! I deployed it via OLM on OpenShift 4.10 and would like to override some config from `flink-operator-config` CM. When I override a value manually, it persists (which is strange - it's a resource managed via Operator) so when I change a value in CM and restart Operator, it works. How can I give the parameters I want while installing the operator? Some operators support setting environment variables in `Subscription` object but I couldn't find such a thing in the documentation. I can do it easily with Helm installation but I want to use OLM. It'd be appreciated if you can guide me. Many many thanks!



--
This message was sent by Atlassian Jira
(v8.20.10#820010)