[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=17796210#comment-17796210 ] dongwoo.kim commented on FLINK-33454: - [~ryanvanhuuksloot] sorry for the late reply, thanks for your efforts :) > 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 > Labels: pull-request-available > Fix For: kubernetes-operator-1.8.0 > > > 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 > 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)
[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=17794792#comment-17794792 ] Ryan van Huuksloot commented on FLINK-33454: PR available. Happy to collaborate [~dongwoo.kim]. I had already written a draft of the code before I looked for an issue - we have a fork internally. Feel free to comment on the issue. > 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 > Labels: pull-request-available > > 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 > 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)
[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 > 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)
