You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/05/16 06:10:00 UTC
[jira] [Updated] (FLINK-27609) Tracking flink-version and flink-revision in FlinkDeploymentStatus
[ https://issues.apache.org/jira/browse/FLINK-27609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated FLINK-27609:
-----------------------------------
Labels: pull-request-available (was: )
> Tracking flink-version and flink-revision in FlinkDeploymentStatus
> ------------------------------------------------------------------
>
> Key: FLINK-27609
> URL: https://issues.apache.org/jira/browse/FLINK-27609
> Project: Flink
> Issue Type: Improvement
> Components: Kubernetes Operator
> Affects Versions: kubernetes-operator-0.1.0
> Reporter: Matyas Orhidi
> Assignee: Matyas Orhidi
> Priority: Major
> Labels: pull-request-available
> Fix For: kubernetes-operator-1.0.0
>
>
> The rest api can provide accurate versioning information through the config endpoint:
> [https://nightlies.apache.org/flink/flink-docs-master/docs/ops/rest_api/#config]
> The operator should propagate such fields in the status:
> * flink-version
> * flink-revision
> This greatly improves the ability to identify malicious Flink versions (CVE affected, deprecated, etc.) in managed environments.
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)