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 2020/08/25 08:06:00 UTC

[jira] [Closed] (FLINK-16699) Support accessing secured services via K8s secrets

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

Till Rohrmann closed FLINK-16699.
---------------------------------
    Resolution: Fixed

Fixed via 8d2c969a83a6830f52b230a00424ddd4f4795a3d

> Support accessing secured services via K8s secrets
> --------------------------------------------------
>
>                 Key: FLINK-16699
>                 URL: https://issues.apache.org/jira/browse/FLINK-16699
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Deployment / Kubernetes
>            Reporter: Canbin Zheng
>            Assignee: zl
>            Priority: Major
>              Labels: pull-request-available, usability
>             Fix For: 1.12.0
>
>
> Kubernetes [Secrets|https://kubernetes.io/docs/concepts/configuration/secret/] can be used to provide credentials for a Flink application to access secured services.  This ticket proposes to 
>  # Support to mount user-specified K8s Secrets into the JobManager/TaskManager Container
>  # Support to use a user-specified K8s Secret through an environment variable.



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