Closed zhixiongdu027 closed 2 years ago
@tao12345666333 @leslie-tsang PLAT
@tao12345666333 @tzssangglass Hi: Sorry, I set a wrong issues title.
I don't actually want to know how the script or job to build a k8s cluster is defined.
What I want to know is why this CI fails, and there is no prompt message. ubuntu-18.04, linux_openresty (ubuntu-18.04, linux_openresty_1_17)
In fact, using kind to create a k8s cluster has been successful. (ubuntu-18.04, linux_openresty_1_17)
and using minikube to create a k8s cluster has been failed . chaos-test
and using minikube to create a k8s cluster has been failed . chaos-test
Hello there, chaos test failed due to dependencies relying on deprecated git protocol, plz check #6073 out.
In fact, using kind to create a k8s cluster has been successful. (ubuntu-18.04, linux_openresty_1_17)
I suspect there is not enough memory to launch both basic CI env and k8s service. more detail in #5200
I suspect there is not enough memory to launch both basic CI env and k8s service. more detail in #5200
if so, What can I do . Creating a new cluster is a necessary condition for test k8s discovery module .
I suspect there is not enough memory to launch both basic CI env and k8s service. more detail in #5200
if so, What can I do . Creating a new cluster is a necessary condition for test k8s discovery module .
Try to run your test suites in a separated github action workflow, so that you don't have to launch a couple of components which are not related to your cases.
I got your point. Maybe it can work ,but wiil be always failed in other ci
Maybe it can work ,but wiil be always failed in other ci
docs/zh/latest/discovery/kubernetes.md
41:43 ❌ unexpected trailing whitespace
(EditorConfig trim_trailing_whitespace https://goo.gl/oo8iVb)
47:14 ❌ unexpected trailing whitespace
(EditorConfig trim_trailing_whitespace https://goo.gl/oo8iVb)
50:80 ❌ unexpected trailing whitespace
(EditorConfig trim_trailing_whitespace https://goo.gl/oo8iVb)
docs/zh/latest/discovery/kubernetes.md:41:43 MD009/no-trailing-spaces Trailing spaces [Expected: 0 or 2; Actual: 6]
docs/zh/latest/discovery/kubernetes.md:47:14 MD009/no-trailing-spaces Trailing spaces [Expected: 0 or 2; Actual: 1]
docs/zh/latest/discovery/kubernetes.md:50:80 MD009/no-trailing-spaces Trailing spaces [Expected: 0 or 2; Actual: 1]
docs/zh/latest/discovery/kubernetes.md:85:1 MD037/no-space-in-emphasis Spaces inside emphasis markers [Context: "> _"]
docs/zh/latest/discovery/kubernetes.md:92 MD028/no-blanks-blockquote Blank line inside blockquote
docs/zh/latest/discovery/kubernetes.md:94 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "> + mTLS"]
docs/zh/latest/discovery/kubernetes.md:98 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "> 所以只实现了 token 的方式, 这也意味着不支持 k..."]
docs/zh/latest/discovery/kubernetes.md:101 MD028/no-blanks-blockquote Blank line inside blockquote
docs/zh/latest/discovery/kubernetes.md:104 MD035/hr-style Horizontal rule style [Expected: -------; Actual: ------]
docs/zh/latest/discovery/kubernetes.md:106 MD012/no-multiple-blanks Multiple consecutive blank lines [Expected: 1; Actual: 2]
Try to run your test suites in a separated github action workflow, so that you don't have to launch a couple of components which are not related to your cases.
It should work. 🤣
@leslie-tsang I mean even if I can create a new ci just for testing kubernetes.t But kubernetes.t will still run in centos-ci , build-ci and will eventually fail
maybe we can split test cases into two or more ci ?
Issue description
4880
In this Pr, I added some code to set up a k8s cluster. common.sh
but it looks like it fails with no clear error message.
someone can help! TKS ~_~
Environment
apisix version
):uname -a
):nginx -V
oropenresty -V
):curl http://127.0.0.1:9090/v1/server_info
to get the info from server-info API):luarocks --version
):