OK, ping me whenever an external ACK cluster is needed.
wangsheng <2213335...@qq.com.invalid> 于2022年12月7日周三 19:21写道：
> Perhaps we should currently schedule our testing tasks step by step,
> similar to we can test single master deployments in a minikube cluster
> built-in by Github Action.
>
> >
Perhaps we should currently schedule our testing tasks step by step, similar to
we can test single master deployments in a minikube cluster built-in by Github
Action.
> 2022年12月7日 下午7:18，Keyong Zhou 写道：
>
> Hi Pan and Binjie,
>
> What's your opinion about the external cluster, shall we add
Hi Pan and Binjie,
What's your opinion about the external cluster, shall we add another
k8s(ACK indeed) cluster, or shall we just use the current ecs cluster and
deploy k8s environment on it?
Thanks,
Keyong Zhou
Cheng Pan 于2022年12月7日周三 17:58写道：
> Hi Binjie,
>
> Thanks for bringing up this
Hi Binjie,
Thanks for bringing up this discussion, I think leverage GitHub Action and
Minicube/K3s is the first step we can do, but considering that GitHub
Runner has 7G memory limitation(I don’t know about cpu limitation), I’m not
sure if we can test Master HA mode on that.
And thanks Keyong
Hi Zhou,
Thanks for your info about the External Kubernetes Cluster.
I will enrich the solution in case of using External Kubernetes Cluster.
From my opinion, using an external Kubernetes cluster will improve the speed of
CI by a large margin over using a built-in Kubernetes cluster.
Anyway,
