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.
- Updates Ingress-Controller Version to 0.19.0
- Adds Service Account for Ingress-Controller
- Adds Support for Prometheus
- Fixes bug with TCP/UDP ConfigMaps not Loading
- Adds more resource limits to default-backend
- Use new ingress class name
- Use app.kubernetes.io/xxxxxxxxxxx labels
Previously we were mixed between the two forms. This commit picks %v,
which is consistent with the Kubernetes code base. They both effectively
do the same thing in this case, though %v works with any object, and %s
only with string objects.
Make future failures to this test easier to debug. Here's an example of
the test failure I ran into:
--- FAIL: TestFunctional/EnvVars (0.58s)
cluster_env_test.go:36: SetEnvFromEnvCmdOutput: Error: No variables were parsed from docker-env output:
set -gx DOCKER_TLS_VERIFY "1";
set -gx DOCKER_HOST "tcp://192.168.39.199:2376";
set -gx DOCKER_CERT_PATH "/usr/local/google/home/tstromberg/.minikube/certs";
set -gx DOCKER_API_VERSION "1.35";
# Run this command to configure your shell:
# eval (minikube docker-env)
* Separate start args from args passed to every command. This is so
that we can call `minikube logs` and `minikube status` with the proper
flags (for the bootstrapper)
* Add a NewMinikubeRunner function to make getting a minikube runner
easier.
We were using an alpha v1.6 kubectl to run 1.5 and 1.6 branches of
minikube at the same time. Since we've merged in 1.6, we will always
use 1.6 kubectl. I've updated the slaves to have it.
In TestStartStop(), check for stopped status once in 5 seconds,
up to 30 seconds, instead of always sleeping for 30 seconds
before stopping it. That way we can reduce duration of the test.
To do that, we need to split out MinikubeRunner.CheckStatus() into
CheckStatusNoFail() that doesn't lead to T.Fatalf(). Other call sites
of CheckStatus() would not be then affected.
priyawadhwa
Thomas Strömberg
Balint Pato
Fernando Diaz
dlorenc
kairen
ulyssessouza
Matt Rickard
dlorenc
Matt Rickard
Aaron Prindle
Dongsu Park
Jimmi Dyson