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

Posted to issues@flink.apache.org by "Gyula Fora (Jira)" <ji...@apache.org> on 2023/12/08 15:49:00 UTC

[jira] [Commented] (FLINK-33454) Adding tls configuration to IngressSpec

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

Gyula Fora commented on FLINK-33454:
------------------------------------

[~dongwoo.kim] , I have assigned this ticket to [~ryanvanhuuksloot] as he expressed interest about working on this.

> Adding tls configuration to IngressSpec
> ---------------------------------------
>
>                 Key: FLINK-33454
>                 URL: https://issues.apache.org/jira/browse/FLINK-33454
>             Project: Flink
>          Issue Type: New Feature
>          Components: Kubernetes Operator
>            Reporter: dongwoo.kim
>            Assignee: Ryan van Huuksloot
>            Priority: Minor
>
> Hello, I want to propose new configuration parameter for IngressSpec.
> Currently flink k8s operator creates ingress resource as we define but it doesn't support tls configuration to secure ingress. 
> How about adding tls parameter on IngressSpec?
> *IngressSpec*
> tls: IngressTLS
> *IngressTLSSpec*
> Hosts: List<String>
> SecretName: String 
> If we could reach an agreement I'll be glad to take on the implementation.
> Thanks in advance.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)