Tested sample pod on Kaapana with runc environment and Kata Environment. So both pods can run simultaneously.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Oct 21 2021
Oct 19 2021
Aug 26 2021
Aug 20 2021
Aug 12 2021
Jul 30 2021
Jul 29 2021
Jul 6 2021
Jul 1 2021
When I install Kaapana using installation script the containerd version is 1.2.5 which is 2 years old.
Jun 30 2021
Jun 24 2021
Jun 22 2021
Successfully tested the Microk8s integration of Kata in a container env (Google Cloud Instance)
Except for the GPU installation/configuration with Kata all others as 1-2 days of work. GPU is definitely possible with Kata, but there are multiple installation and drivers and kernel configurations are recommended by them, and I am not much familiar with GPU installation and configurations before in a server system, rest everything I will change to a sub task now.
Jun 21 2021
Jun 11 2021
Jun 9 2021
changing the status to Resolved Since Kata is successfully tested in the first stage.
Managed to run a test run with nginx server in a normal environment and Kata environment with two different kernels, so it is possible to create a diff kernel using Kata
Jun 1 2021
closing gVisor experiments since Kata is our first choice and Kata is able to run in our bare-metal machine, hence temporarily closing gVisor testing.
Closing the issue since gVisor has lots of limitations with microk8s and our current Kaapana architecture.
Apr 20 2021
Apr 8 2021
Reply from Gvisor Team
Apr 1 2021
Mar 31 2021
Created a bug in google gvisor, and one guy is helping us.
Mar 25 2021
ubuntu@gvisor-san:~$ minikube start --container-runtime=containerd --docker-opt containerd=/var/run/containerd/containerd.sock 😄 minikube v1.18.1 on Ubuntu 18.04 (amd64) ✨ Using the docker driver based on existing profile 👍 Starting control plane node minikube in cluster minikube 🏃 Updating the running docker "minikube" container ... 🌐 Found network options: ▪ NO_PROXY=localhost,127.0.0.1,169.254.169.254,dkfz-heidelberg.de,192.168.49.2,10.96.0.0/12,192.168.99.0/24,192.168.39.0/24 ▪ http_proxy=http://www-int2.dkfz-heidelberg.de:80 ▪ https_proxy=http://www-int2.dkfz-heidelberg.de:80 ▪ no_proxy=localhost,127.0.0.1,169.254.169.254,dkfz-heidelberg.de,192.168.49.2,10.96.0.0/12,192.168.99.0/24,192.168.39.0/24 ❗ This container is having trouble accessing https://k8s.gcr.io
Discussion from Tech meeting (Hanno, Klaus, Marco)
Mar 18 2021
check with microk8s - kata microk8s current system
Mar 17 2021
Kata-supported platforms are given below.
Mar 10 2021
Mar 8 2021
Feb 25 2021
Issue in landing page tfda, base pods .
Feb 24 2021
Feb 19 2021
Feb 11 2021
Feb 2 2021
@schererj Thank you after tomorrows retreat, I will work on these fixes (tfda)