You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Zhu Zhu (Jira)" <ji...@apache.org> on 2019/12/24 02:32:00 UTC
[jira] [Assigned] (FLINK-15354) Start and stop minikube only in
kubernetes related e2e tests
[ https://issues.apache.org/jira/browse/FLINK-15354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Zhu Zhu reassigned FLINK-15354:
-------------------------------
Assignee: Zhu Zhu
> Start and stop minikube only in kubernetes related e2e tests
> ------------------------------------------------------------
>
> Key: FLINK-15354
> URL: https://issues.apache.org/jira/browse/FLINK-15354
> Project: Flink
> Issue Type: Bug
> Reporter: Yang Wang
> Assignee: Zhu Zhu
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently, we start minikube in {{nightly.sh for every e2e test}}, and it will never be stopped. It is unnecessary and will occupy some resources on travis. I think the minikube should only be started in the kubernetes related test(\{{test_kubernetes_embedded_job.sh}}) and need to be stopped once the test finished.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)