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 2022/07/18 12:16:00 UTC

[jira] [Commented] (FLINK-28593) Introduce default ingress templates at operator level

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

Gyula Fora commented on FLINK-28593:
------------------------------------

I think instead of making this specifc to ingresses I would like to allow FlinkDeployment / FlinkSessionJob spec defaults on the operator level. It's not completely clear to me yet how would it be best to introduce these so we should discuss on the mailing list.

Some approaches:
 - Global spec defaults
 - Per namespace spec defaults
 - Dynamic logic with some pluggable mechanism

> Introduce default ingress templates at operator level
> -----------------------------------------------------
>
>                 Key: FLINK-28593
>                 URL: https://issues.apache.org/jira/browse/FLINK-28593
>             Project: Flink
>          Issue Type: Improvement
>          Components: Kubernetes Operator
>            Reporter: Matyas Orhidi
>            Priority: Major
>             Fix For: kubernetes-operator-1.2.0
>
>
> Ingress templates are currently [defined at CR level|https://nightlies.apache.org/flink/flink-kubernetes-operator-docs-main/docs/operations/ingress/], but these rules can be enabled globally at operator level too.



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