[
https://issues.apache.org/jira/browse/FLINK-30519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-30519:
-----------------------------------
Labels: stale-assigned stale-critical starter (was: stale-assigned 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
Critical but is unassigned and neither itself nor its Sub-Tasks have been
updated for 14 days. I have gone ahead and marked it "stale-critical". If this
ticket is critical, please either assign yourself or give an update.
Afterwards, please remove the label or in 7 days the issue will be
deprioritized.
> Add e2e tests for operator dynamic config
> -----------------------------------------
>
> Key: FLINK-30519
> URL: https://issues.apache.org/jira/browse/FLINK-30519
> Project: Flink
> Issue Type: Technical Debt
> Components: Kubernetes Operator
> Reporter: Gyula Fora
> Priority: Critical
> Labels: stale-assigned, stale-critical, starter
>
> The dynamic config feature is currently not covered by e2e tests and is
> subject to accidental regressions, as shown in:
> https://issues.apache.org/jira/browse/FLINK-30329
> We should add an e2e test that covers this
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
