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

Posted to issues@flink.apache.org by "Till Rohrmann (Jira)" <ji...@apache.org> on 2021/03/02 17:45:00 UTC

[jira] [Comment Edited] (FLINK-21521) Pretty print K8s specifications

    [ https://issues.apache.org/jira/browse/FLINK-21521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17293866#comment-17293866 ] 

Till Rohrmann edited comment on FLINK-21521 at 3/2/21, 5:44 PM:
----------------------------------------------------------------

Fixed via 

1.13.0: 9874f017715651022c02f30720d33e85662c2277
1.12.3: b0609a6a89d17c5b1258bcf26ae957d2613d4f6e


was (Author: till.rohrmann):
Fixed via 9874f017715651022c02f30720d33e85662c2277

> Pretty print K8s specifications
> -------------------------------
>
>                 Key: FLINK-21521
>                 URL: https://issues.apache.org/jira/browse/FLINK-21521
>             Project: Flink
>          Issue Type: Improvement
>          Components: Deployment / Kubernetes
>    Affects Versions: 1.12.1, 1.13.0
>            Reporter: Till Rohrmann
>            Assignee: Yang Wang
>            Priority: Major
>              Labels: pull-request-available, usability
>             Fix For: 1.13.0, 1.12.3
>
>
> When turning on the {{DEBUG}} log level, then Flink's K8s integration logs the specifications of started K8s resources (e.g. JobManager/TaskManager pods). From a user's perspective this is pretty helpful because it tells him what Flink is launching. In order to better read the specification it would be even better if we could print the yaml with proper indentation (pretty print).
> cc [~fly_in_gis]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)