Kata is tested successfully and this has to be integrated with TFDA MVP, and a couple more TODO and checks are needed.
|Open||s669m||T28541 Roadmap and TODO using Kata Container|
|Resolved||s669m||T28567 Microk8s Integration of Kata and Testing|
|Open||s669m||T28568 Create an Auto Installation and Configuration of Kata with Microk8s Script (Bash)|
|Open||s669m||T28569 Test GPU in Kata container|
|Resolved||s669m||T28570 Compatibility Test with Kaapana Microk8s and Containerd Tech stack|
|Open||s669m||T28571 DKFZ Open-stack Kata possibility ( Follow-up with ITCF Team)|
|Open||s669m||T28572 Auto-Deploy the pods via helm in a Kata Env|
|Open||s669m||T28573 Integrating with Airflow/Workflow (Kata Env)|
|Open||s669m||T28574 Integrating Kata with Further MVP's|
|Resolved||s669m||T28575 Test Kata with Sample workloads in a Kaapana env|
|Open||s669m||T28576 Cilium Integration with Kata possibilities|
It seems to me that most of this points are at least 1-2 work days worth of time. If this right it would make sense to turn them into subtasks. Then we also have a clearer burn up, because one can explicitly marke sub tasks as done...
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.