[
https://issues.apache.org/jira/browse/FLINK-28272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matyas Orhidi updated FLINK-28272:
----------------------------------
Fix Version/s: kubernetes-operator-1.2.0
(was: kubernetes-operator-1.1.0)
> Handle TLS Certificate Renewal in Webhook
> -----------------------------------------
>
> Key: FLINK-28272
> URL: https://issues.apache.org/jira/browse/FLINK-28272
> Project: Flink
> Issue Type: Bug
> Components: Kubernetes Operator
> Affects Versions: kubernetes-operator-1.0.0
> Reporter: Matyas Orhidi
> Priority: Major
> Fix For: kubernetes-operator-1.2.0
>
>
> We found that flink-kubernetes-operator v1.0.0 does not reload new
> certificate when updated by cert-manager, and it causes the following error
> when updating FlinkDeployment
> {{Failed sync attempt to 597d35a7434bede526f526852c33a65262765219: one or
> more objects failed to apply, reason: Internal error occurred: failed calling
> webhook "flinkoperator.flink.apache.org": Post "}}
> {{[https://flink-operator-webhook-service.flink-operator.svc:443/validate?timeout=10s|https://flink-operator-webhook-service.flink-operator.svc/validate?timeout=10s]}}
> {{": x509: certificate signed by unknown authority (possibly because of
> "x509: invalid signature: parent certificate cannot sign this kind of
> certificate" while trying to verify candidate authority certificate
> "FlinkDeployment Validator") (retried 3 times).}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)