Commit Graph

18 Commits (f5a859a383bccaa7cbd74dc30d3740df35b2404f)

Author SHA1 Message Date
Sharif Elgamal 8547aece43 point to latest gvisor addon image 2020-02-19 15:56:52 -08:00
tstromberg 9dfa1bfe6c Pull a specific version instead of latest, to avoid compatibility issues between addon and pushed images 2019-10-25 14:48:45 -07:00
tstromberg 9b2ce99723 Use chroot instead of LD_LIBRARY_PATH for containerd restart 2019-10-25 14:03:01 -07:00
Ian Lewis d8c380da85
Merge branch 'master' into gvisor-containerd-shim_v0.0.2 2019-09-03 22:20:12 -04:00
Ian Lewis d14bdbced7 Update gvisor runsc version
- Updates the gvisor addon to use containerd shim v2
- Updates the version of runsc
- Auto-installs a gvisor RuntimeClass

Issue #4482
2019-08-26 05:02:22 +00:00
Anders F Björklund ae8894c0ca Stop using no_pivot when not using rootfs 2019-08-24 16:12:52 +02:00
Priya Wadhwa cdbb2dd572 Updated gvisor test 2019-08-05 15:21:09 -07:00
Priya Wadhwa d68e054dfd Attempt to copy gvisor tar and load with ctr 2019-07-11 11:58:57 -07:00
Priya Wadhwa 3ffe2af1e4 Point docker daemon to minikube and rebuild docker image 2019-07-10 16:14:46 -07:00
Priya Wadhwa e6653b78eb Build and push the gvisor image, setting an environment variable
which can be picked up during integration testing.

I opted to do it this way because the locally built gvisor image wasn't
being picked up by minikube, because the docker daemon wasn't
configured, since minikube isn't up and running yet. Even if the docker daemon was configured to point to
minikube, we wouldn't be able to build the gvisor-image from the test
itself.
2019-07-10 14:13:17 -07:00
Priya Wadhwa d2e5a4b052 build gvisor image locally in integration tests; add temporary error to make sure that image is used 2019-07-09 12:46:57 -07:00
Priya Wadhwa a8f1ed7a26 Rebuild gvisor image for integration tests
We should rebuild the gvisor image for integration tests, so that if
changes are made to the gvisor image they are tested. I added an
environment variable that, when set, will change the expected gvisor
image repo.
2019-07-08 15:54:30 -07:00
Medya Gh d688240b75 Rename all template files to be consistent format .ext.tmpl 2019-05-06 15:12:46 -07:00
Zhongcheng Lao 7a59d376cf Turn addon resource with images into template
When the user overrides image repository the images will be pulled
from the overrided one instead of the official repositories.
2019-02-18 01:00:18 +08:00
Anders F Björklund 6ff11e44a5 Remove default cni flags from the documentation 2019-02-05 20:05:05 +01:00
Martynas Pumputis d982c4bf74 Do not include the default CNI config by default
Previously, minikube has been shipped with the default CNI config
(/etc/cni/net.d/k8s.conf) in its rootfs. This complicated a lot
when using a custom CNI plugin, as the default config was picked
by kubelet before the custom CNI plugin has installed its own CNI
config. So, the end result was that some Pods were attached to a
network defined in the default config, and some got managed by
the custom plugin.

This commit introduces the flag "--enable-default-cni" to
"minikube start" to trigger the provisioning of the default CNI
config.

Signed-off-by: Martynas Pumputis <m@lambda.lt>
2019-01-03 09:23:29 +01:00
priyawadhwa 1514511b7a Change restart policy on gvisor pod (#3445)
* Change restart policy on gvisor pod

Change the restart policy on the gvisor pod to Always. This way, if a
user runs

minikube addons enable gvisor
minikube stop
minikube start

when the addon manager tries to restart the gvisor pod, it will be
restarted and gvisor will start running automatically. This PR also adds an
integration test for this functionality.

* Test stop and start

* Revert test to delete

Revert test to delete for now, for some reason "stop" and then "start"
is failing both locally and in Jenkins for VirtualBox with a "panic test
timed out after 30 min" error
2018-12-11 18:39:57 -08:00
priyawadhwa 8f128a7d10 Enable gvisor addon in minikube (#3399)
This PR adds the code for enabling gvisor in minikube. It adds the pod
that will run when the addon is enabled, and the code for the image
which will run when this happens.

When gvisor is enabled, the pod will download runsc and the
gvisor-containerd-shim. It will replace the containerd config.toml and
restart containerd.

When gvisor is disabled, the pod will be deleted by the addon manager.
This will trigger a pre-stop hook which will revert the config.toml to
it's original state and restart containerd.
2018-12-07 15:27:22 -08:00