[
https://issues.apache.org/jira/browse/FLINK-40195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebastian Struß updated FLINK-40195:
------------------------------------
Summary: Flink kubernetes operator certificate secret name should not
collide with other operators (was: Flink kubernetes operator certificate
secret name should be configurable)
> Flink kubernetes operator certificate secret name should not collide with
> other operators
> -----------------------------------------------------------------------------------------
>
> Key: FLINK-40195
> URL: https://issues.apache.org/jira/browse/FLINK-40195
> Project: Flink
> Issue Type: Improvement
> Components: Kubernetes Operator
> Affects Versions: kubernetes-operator-1.15.0
> Reporter: Sebastian Struß
> Priority: Major
> Labels: pull-request-available
>
> Currently the helm chart for the flink kubernetes operator does not support
> customizing the name for the certificate secret.
> Since it is using a generic name, this easily leads to collision when using
> other operators (that also currently do not allow to specify the name of said
> secret).
> This pull request is a suggestion on how to fix this issue, however it will
> might cause cert manager to create a new certificate.
> If this is not wanted, i could imagine adding a hook for migration or to add
> a migration flag. This migration flag, when enabled (default), would simply
> change the secret name and when disabled would simply keep the original
> static name for backwards compatibility.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
