flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Flink Jira Bot (Jira)" <j...@apache.org>
Subject [jira] [Updated] (FLINK-20215) Keep the "Access the Flink UI " document same in “Kubernetes Setup” and "Native Kubernetes Setup Beta"
Date Sun, 30 May 2021 23:16:01 GMT

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

Flink Jira Bot updated FLINK-20215:
    Labels: auto-deprioritized-critical stale-major  (was: auto-deprioritized-critical)

I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help the community
manage its development. I see this issues has been marked as Major but is unassigned and neither
itself nor its Sub-Tasks have been updated for 30 days. I have gone ahead and added a "stale-major"
to the issue". If this ticket is a Major, please either assign yourself or give an update.
Afterwards, please remove the label or in 7 days the issue will be deprioritized.

> Keep the "Access the Flink UI " document same in “Kubernetes Setup” and "Native Kubernetes
Setup Beta"
> ------------------------------------------------------------------------------------------------------
>                 Key: FLINK-20215
>                 URL: https://issues.apache.org/jira/browse/FLINK-20215
>             Project: Flink
>          Issue Type: Improvement
>          Components: Documentation
>    Affects Versions: 1.12.0
>            Reporter: Guowei Ma
>            Priority: Major
>              Labels: auto-deprioritized-critical, stale-major
> Both the "https://ci.apache.org/projects/flink/flink-docs-release-1.11/ops/deployment/native_kubernetes.html"
and "https://ci.apache.org/projects/flink/flink-docs-release-1.11/ops/deployment/native_kubernetes.html#accessing-job-manager-ui"
have a section about "how to access the Flink UI".
> But the description is a little different from each other, I think maybe we could make
them same.

This message was sent by Atlassian Jira

View raw message