You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Matthias Pohl (Jira)" <ji...@apache.org> on 2023/02/03 07:58:00 UTC

[jira] [Commented] (FLINK-30893) Replace not specifying a driver in Minikube by something else

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

Matthias Pohl commented on FLINK-30893:
---------------------------------------

I'm going to label this one as {{starter}} because fixing the minikube setup doesn't require in-depth knowledge of Flink.

> Replace not specifying a driver in Minikube by something else
> -------------------------------------------------------------
>
>                 Key: FLINK-30893
>                 URL: https://issues.apache.org/jira/browse/FLINK-30893
>             Project: Flink
>          Issue Type: Technical Debt
>          Components: Test Infrastructure
>    Affects Versions: 1.17.0, 1.15.3, 1.16.1
>            Reporter: Matthias Pohl
>            Priority: Major
>              Labels: starter
>
> Quoting [~wangyang0918] here from a [Github PR comment|https://github.com/apache/flink/pull/21837#pullrequestreview-1282199706]:
> {quote}
> We need to find a more elegant way to avoid none driver of minikube in the future. And then we could rely on the latest minikube version and find some potential incompatible problems with new K8s versions.
> {quote}



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