- 30 11月, 2018 3 次提交
-
-
由 Thomas Stromberg 提交于
-
由 Thomas Stromberg 提交于
-
由 Thomas Stromberg 提交于
-
- 28 11月, 2018 5 次提交
-
-
由 Anders Björklund 提交于
Closes #3295
-
由 Balint Pato 提交于
-
由 Balint Pato 提交于
* even longer timeout + timeout error is retriable now * fix for debugging when tunnel test has issues
-
由 Peeyush gupta 提交于
-
由 Thomas Strömberg 提交于
* Restrict TestDocker commands to 10 minutes of total runtime. * Hide unneccesarily scary delete error
-
- 27 11月, 2018 3 次提交
-
-
由 Fernando Diaz 提交于
Updates the Ingress-Nginx Addon to version 0.21.
-
由 Balint Pato 提交于
Small improvements to debugging and reducing integration test flakiness: * added logging to kubeadm init in the SSHExecutor * increasing timeout for RBAC creation via the kubernetes client set * only log tunnel output to test logger
- 25 11月, 2018 1 次提交
-
-
由 Ihor Dvoretskyi 提交于
Removed bash welcome symbols ('$' symbols) for easier copy&paste. Signed-off-by: NIhor Dvoretskyi <ihor@linux.com>
-
- 22 11月, 2018 2 次提交
-
-
由 Prakhar Goyal 提交于
The documentation is clearer now for a person new to macOS.
-
由 Balint Pato 提交于
This change is a bit of a hack to make IP routing work over the virtio-net interface - it forces the virtio-net interface (bridge100) created by hyperkit/xhyve to reset via removing and readding the single member of the interface. Without this "reset" packets are just simply lost most of the time, despite a completely healthy IP route. This error was also the reason for a large percentage of our integration test failures. While reducing the flakiness of tunnel related tests I also increased the timeout requirement and adding retries to the nginx request in TestTunnel.
-
- 20 11月, 2018 2 次提交
-
-
由 Thomas Strömberg 提交于
Add timeout to testDashboard, skip testTunnel if sudo password is required.
-
由 Thomas Strömberg 提交于
Fix invalid build result comparison in the cross build script
-
- 17 11月, 2018 1 次提交
-
-
由 priyawadhwa 提交于
After stopping any runtimes that aren't being used, if we're using containerd then we need to restart it. This is because it competes with cri-o to listen on port 10010, causing a necesary plugin to not be installed. After stopping cri-o, we need to restart containerd so that the plugin is installed. I also added some preflight checks when using alternative runtimes. kubeadm checks to make sure the Docker service is running, so I disabled that. It also checks if a few ports are available; these are ports that containerd uses, so I also added them to the ignore list. This should finish the work started in #3211, which stopped alternative runtimes but didn't restart containerd. I was able to run "minikube start" with containerd locally with this change.
-
- 16 11月, 2018 3 次提交
-
-
由 Thomas Strömberg 提交于
-
由 Balint Pato 提交于
to reuse the same jenkins jobs, I just added extra logic into the current scripts, namely: for cases when `$ghprbPullId` equals "master", we ignore setting the github statuses.
-
由 dlorenc 提交于
-
- 15 11月, 2018 2 次提交
-
-
由 Anders Björklund 提交于
* Stop extra container runtimes, before bootstrapper The minikube.iso starts every runtime, by default * Disable docker-env output, if docker isn't running Might be running an alternative container runtime
-
由 Anders Björklund 提交于
* Add config parameter for the cri socket path Closes #3153 * Remove stray newline, when not using criSocket * Add the --cri-socket parameter to configuration Also fix the syntax for CRI-O, adding unix://
-
- 14 11月, 2018 3 次提交
-
-
由 gaoyawei616 提交于
-
由 Thomas Stromberg 提交于
-
由 Thomas Strömberg 提交于
Upgrade to crio v1.11.8
-
- 13 11月, 2018 7 次提交
-
-
由 Alexander Ilyin 提交于
-
由 Yongkun Anfernee Gui 提交于
New drivers should be added into org https://github.com/machine-drivers. Fix #2953
-
由 mooncake 提交于
Signed-off-by: Nmooncake <xcoder@tenxcloud.com>
-
由 xichengliudui 提交于
-
由 Nguyen Hai Truong 提交于
Small modification to correct spelling mistake.
-
由 Thomas Strömberg 提交于
Add timeout when reading dashboard host:port from kubectl
-
由 Thomas Stromberg 提交于
-
- 10 11月, 2018 4 次提交
-
-
由 Thomas Stromberg 提交于
-
由 Thomas Stromberg 提交于
-
由 Thomas Stromberg 提交于
-
由 Thomas Stromberg 提交于
kubectl releases older than August 2017 don't include a newline, which means there is effectively no hint that the output has completed. I believe this is why tests have been failing on the macOS. Should resolve test timeout panics such as #3203
-
- 08 11月, 2018 4 次提交
-
-
由 Thomas Stromberg 提交于
This test typically takes <30s to execute, so 180s should leave plenty of margin for error.
-
由 Thomas Stromberg 提交于
-
由 Thomas Stromberg 提交于
-
由 Thomas Stromberg 提交于
-