You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Till Rohrmann (Jira)" <ji...@apache.org> on 2020/01/14 09:52:00 UTC

[jira] [Resolved] (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 ]

Till Rohrmann resolved FLINK-15354.
-----------------------------------
    Resolution: Fixed

Fixed via

master: 6cf5940480aec6c0e0d5ba22e1c3d2397229349a
1.10.0: 9c0bd30218bf4cd7f823ff40161ee315f9084b0f

> 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: Yang Wang
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.10.0
>
>          Time Spent: 20m
>  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)