AbdelrahmanElawady

After looking into how updates work in zos, disk workloads don't consider any changes other than disk size and indeed they don't consider it changed unless size changed. After discussions...

After looking into it with @sameh-farouk, both issues are caused by zos ignoring the disk changes. The reason for timing out in case of deleting has nothing to with VM....

We can utilize `goreleaser` [nFPM](https://goreleaser.com/customization/nfpm/) to manage generating deb, rpm, apk and archlinux packages. It can manage the package's requirements, conflicts, recommended packages and suggested packages. We can also specify...

It's an issue with cloud-container not continuing network configuration if an error happens which leads to empty `/etc/resolv.conf` file (among maybe other things). https://github.com/threefoldtech/cloud-container/issues/20

Here is a list of the tasks after discussion on KubeArmor slack: - Configure Container Runtime and Hosts: - Setup the right runtime hooks with the right conditions. i.e. on...

Container created before KubeArmor now are handled with a simple detached process that waits on KubeArmor to start then sends all previous containers.

Also, in order to try out this PR. You only need to build this code and run it on a CRI-O Kubernetes cluster and operator with snitch will take care...