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

Flink Jira Bot updated FLINK-30327:
-----------------------------------
    Labels: stale-major starter  (was: starter)

I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help 
the community manage its development. I see this issues has been marked as 
Major but is unassigned and neither itself nor its Sub-Tasks have been updated 
for 60 days. I have gone ahead and added a "stale-major" to the issue". If this 
ticket is a Major, please either assign yourself or give an update. Afterwards, 
please remove the label or in 7 days the issue will be deprioritized.


> Adding a values.schema.json to the Helm chart source to support schema 
> validation on Helm chart configuration
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: FLINK-30327
>                 URL: https://issues.apache.org/jira/browse/FLINK-30327
>             Project: Flink
>          Issue Type: Improvement
>          Components: Kubernetes Operator
>    Affects Versions: kubernetes-operator-1.2.0
>            Reporter: Matthias Pohl
>            Priority: Major
>              Labels: stale-major, starter
>
> Helm charts support [configuration 
> validation|https://helm.sh/docs/topics/charts/#schema-files] through 
> {{{}values.schema.json{}}}. I'm wondering whether that's something worth 
> adding.



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

Reply via email to