e1f8446886
Merge pull request #4421 from afbjorklund/podman-run
...
Enable running containers with Podman
2019-06-24 09:49:05 +08:00
657469310c
Use retryable http to avoid connection flakes
2019-06-13 22:58:14 -07:00
8e4c6c9922
Update releases.json to include v1.1.1
2019-06-07 14:30:39 -07:00
b31c66c807
Link runc dynamically, avoid docker-runc install
...
Static linking doesn't work with the systemd cgroup manager.
The latest docker package now uses the standard runc program.
2019-06-04 07:13:59 +02:00
32583d8c1f
Install podman configuration to use no_pivot_root
...
We need this podman setting, as long as we're running from rootfs.
no_pivot_root = true
Note that building uses a different way, an environment variable.
export BUILDAH_NOPIVOT=true
2019-06-04 07:13:28 +02:00
70a00bfb3b
Make podman depend on conmon from master
...
Need a later version than the one provided by crio.
So use separate installations, one for each program.
2019-06-04 07:13:09 +02:00
8e650c0c61
Dashboard: add --disable-settings-authorizer to avoid settings 403 forbidden
2019-06-02 22:22:12 +08:00
516904c9a1
Merge pull request #4321 from afbjorklund/podman-buildah
...
Make buildah --no-pivot default, using env var
2019-05-28 17:09:48 -07:00
657221e9d2
Merge pull request #4341 from kumarom/registry-proxy
...
Enable registry-proxy
2019-05-28 10:25:28 -07:00
fb0a6f4548
Make buildah --no-pivot default, using env var
...
Needed for doing "podman build" (uses buildah) when running on rootfs.
This environment variable has the same affect as DOCKER_RAMDISK does.
2019-05-25 13:23:29 +02:00
1a24097cfe
Merge pull request #4340 from amshinde/add-tc-u32-mirred
...
kernel: Add config for tc u32 filter and mirred action
2019-05-24 13:55:33 -07:00
ec3e7b5896
Enable registry-proxy
...
As per [this blog](https://blog.hasura.io/sharing-a-local-registry-for-minikube-37c7240d0615 ) and [this gist](https://gist.github.com/coco98/b750b3debc6d517308596c248daf3bb1 ), we need to deploy a registry-proxy
which will expose docker registry on the minikube host.
Once this daemon set is deployed on minikube, one can access registry on `$(minikube ip):5000`.
This has been tested with minikube v1.0.1 with none driver. With this, one will not have to use
`kubectl port-forward`. I was able to push a container image to registry using
```
docker push $(minikube ip):5000/test-img
```
And then ran it in minikube using
```
kubectl run -i -t test-img --image=$(minikube ip):5000/test-img --restart=Never
```
2019-05-24 10:37:14 +05:30
2176f3fa37
kernel: Add config for tc u32 filter and mirred action
...
These are needed for running Kata Containers in minikube.
Kata uses linux tc for its networking
Signed-off-by: Archana Shinde <archana.m.shinde@intel.com>
2019-05-23 18:34:34 -07:00
6a9031aaf6
Enable GatewayPorts in sshd_config, for proxying in services into minikube
2019-05-24 09:56:49 +09:00
3b0b33f704
Update releases.json to include v1.1.0
2019-05-22 00:21:08 +00:00
af443fc3ac
Merge pull request #4299 from afbjorklund/podman-1.3
...
Update to Podman 1.3 & CRIO v1.14.1
2019-05-20 16:29:43 -07:00
d3c088aefe
Merge branch 'master' into podman-1.3
2019-05-20 22:32:01 +02:00
d6434317c7
Upgrade crio to 1.14.1
2019-05-20 22:31:35 +02:00
dff8960a3c
Upgrade podman to 1.3.1
2019-05-20 22:23:26 +02:00
a3360831f4
Upgrade Docker, from 18.09.5 to 18.09.6
2019-05-20 22:12:05 +02:00
00832dc182
Merge pull request #4204 from afbjorklund/docker-18.09
...
Upgrade Docker, from 18.06.3-ce to 18.09.5
2019-05-20 08:12:55 -07:00
971f53764e
Merge pull request #4207 from afbjorklund/crio.conf
...
Document overrides to the crio.conf
2019-05-20 08:12:13 -07:00
9a9f9edf5f
First pass at lint-ageddon
2019-05-13 18:31:55 -07:00
40da5023d0
Fix registry addon ReplicationController template
...
Running the `minikube addons enable registry` yields `registry was successfully enabled` but no `registry` Pod ends up being run.
I've narrowed it down to this `env` entry not being quoted.
Logs from `kube-addon-manager-minikube` Pod show this error:
```
Error from server (BadRequest): error when creating "/etc/kubernetes/addons/registry-rc.yaml": ReplicationController in version "v1" cannot be handled as a ReplicationController: v1.ReplicationController.Spec: v1.ReplicationControllerSpec.Template: v1.PodTemplateSpec.Spec: v1.PodSpec.Containers: []v1.Container: v1.Container.Env: []v1.EnvVar: v1.EnvVar.Value: ReadString: expects " or n, but found t, error found in #10 byte of ...|,"value":true}],"ima|..., bigger context ...|"name":"REGISTRY_STORAGE_DELETE_ENABLED","value":true}],"image":"registry.hub.docker.com/library/reg|...
```
2019-05-07 22:35:15 +02:00
5fa67141e6
Added Exotic Arch for legacy docker images
2019-05-06 17:07:05 -07:00
d688240b75
Rename all template files to be consistent format .ext.tmpl
2019-05-06 15:12:46 -07:00
c997c72667
Update gitignore
2019-05-06 14:44:59 -07:00
e6c4ee5b50
Rename the .template files to .yaml
2019-05-06 14:43:10 -07:00
1790589f70
Replace ARCH sed macros with Go templates
2019-05-06 14:38:38 -07:00
732c6d7e9b
Need to create the cni directory, or cri-o cries
...
config validation: invalid network_dir:
stat /etc/cni/net.d/: no such file or directory
2019-05-04 22:40:00 +02:00
c272f683ea
The cri-o config changed the type of a field
...
Trying to run with the old config gives fatal runtime error:
toml: cannot load TOML value of type string into a Go slice
2019-05-04 22:09:21 +02:00
8a4b8629dc
Upgrade crio.conf to version v1.14.0
2019-05-04 22:05:23 +02:00
1d8b7d6032
Upgrade crio.conf to version v1.13.0
2019-05-04 21:57:46 +02:00
bfed2948c1
Upgrade crio.conf to version v1.12.0
2019-05-04 21:55:12 +02:00
6dda382a6a
Upgrade crio.conf to version v1.10.0
2019-05-04 19:33:02 +02:00
5927bf874d
Upgrade Docker, from 18.06.3-ce to 18.09.5
...
Stop installing docker-runc, docker-containerd and docker-containerd-ctr
Instead use the upstream runc, containerd and ctr (after upgrading them)
runc v1.0.0-rc6-69-g2b18fe1
containerd v1.2.5
2019-05-04 18:16:37 +02:00
3cc4376298
Upgrade crio to 1.14.0
2019-05-04 16:17:12 +02:00
af5b2c7c2d
Upgrade podman to 1.2.0
2019-05-04 16:10:10 +02:00
fce157865d
Merge pull request #4153 from keramiozsoy/storageclass-its-no-longer-beta
...
storageclass no longer beta #4148
2019-04-30 15:46:05 -07:00
d0a3b6f569
Merge pull request #4091 from linux-on-ibm-z/multi-arch-deploy-support
...
Adding support for s390x
2019-04-30 13:02:28 -07:00
a9e94cfb60
Update releases.json to include v1.0.1
2019-04-29 18:10:55 +00:00
d7892ec104
storageclass no longer beta
...
https://github.com/kubernetes/kubernetes/blob/master/cluster/addons/storage-class/local/default.yaml
2019-04-25 22:17:58 +03:00
9b419d66dc
adding multi-arch support
2019-04-17 08:43:37 -04:00
ce40cdc960
Added REGISTRY_STORAGE_DELETE_ENABLED environment variable for Registry addon
2019-04-11 16:14:36 -07:00
14414d1676
Merge pull request #4030 from laozc/fix-hv-daemon
...
Update Hyper-V daemons
2019-04-10 15:17:40 -07:00
b06b3ee3f8
Enable CONFIG_NF_CONNTRACK_ZONES
2019-04-09 06:50:22 -07:00
9a5f3c2673
Do not attempt to restart service on failures for Hyper-V daemons
...
Service restart may not work when a specific integration service
is disabled in the VM setting. Remove the setting for performance
concerns.
2019-03-31 14:06:56 +08:00
e8cdc4ba85
Merge Hyper-V deamon packages to hyperv-daemons
...
Signed-off-by: Zhongcheng Lao <Zhongcheng.Lao@microsoft.com>
2019-03-31 12:28:00 +08:00
e0d7363fba
Add udev rules to generate devices for Hyper-V daemons
...
Signed-off-by: Zhongcheng Lao <Zhongcheng.Lao@microsoft.com>
2019-03-31 12:27:54 +08:00
def1a55472
Install Hyper-V FCOPY daemon
...
Signed-off-by: Zhongcheng Lao <Zhongcheng.Lao@microsoft.com>
2019-03-31 12:27:23 +08:00
Thomas Strömberg
Medya Gh
minikube-bot
Anders F Björklund
fenglixa
Om Kumar
Archana Shinde
Toliver Jue
Zoran Regvart
kerami
salamani
Himanshu Pandey
Joji Mekkatt
Zhongcheng Lao