vladikr / maroonedpods

Isolating container workloads in Virtual Machines using KubeVirt

MaroonedPods [WIP]

An operator that enables container workloads to be isolated in Virtual Machines using KubeVirt.

Here's a brief overview of how it works:

• Any submitted pod tagged with a "maroonedPods" label will be admitted but will be prevented from scheduling.

• At this point, a new Virtual Machine will be created. It will run a Kubernetes Node image.

• On boot, this VM will register itself as a Node within the cluster, specifically allocated for the awaiting pod.

• As soon as this Node becomes ready, the Scheduling Gate on the pod is removed, allowing it to be scheduled to this newly prepared Node.

MaroonedPods is taking the Kubernetes native approach to the workload isolation problem.
The project lets you run Pod in virtual machines (VMs). These pods can use all the available Kubernetes plugins and access special hardware just like any other app running on KubeVirt VMs.

Screencast.from.2024-02-02.13-23-28.webm

maroonedpods's Issues

Demo upload

Screencast.from.2024-02-02.13-23-28.webm

maroonpods CR is struck in deploying

Looks like all pods are running:

maroonedpods   pod/maroonedpods-controller-6f8d9b58c8-2t89b   1/1     Running   0          58m
maroonedpods   pod/maroonedpods-controller-6f8d9b58c8-ch476   1/1     Running   0          58m
maroonedpods   pod/maroonedpods-operator-8476d74b94-sx8h9     1/1     Running   0          58m
maroonedpods   pod/maroonedpods-server-5946b9bb69-ffw8n       1/1     Running   0          58m
maroonedpods   pod/maroonedpods-server-5946b9bb69-tdr8b       1/1     Running   0          58m
maroonedpods   service/maroonedpods-server           NodePort    10.104.129.105   <none>        443:31791/TCP            58m
maroonedpods   deployment.apps/maroonedpods-controller   2/2     2            2           58m
maroonedpods   deployment.apps/maroonedpods-operator     1/1     1            1           58m
maroonedpods   deployment.apps/maroonedpods-server       2/2     2            2           58m
maroonedpods   replicaset.apps/maroonedpods-controller-6f8d9b58c8   2         2         2       58m
maroonedpods   replicaset.apps/maroonedpods-operator-8476d74b94     1         1         1       58m
maroonedpods   replicaset.apps/maroonedpods-server-5946b9bb69       2         2         2       58m

However, the CR status is still Deploying

cluster-up/kubectl.sh describe maroonedpods -n maroonedpods:

  Warning  UpdateResourceFailed   7m59s (x21 over 63m)  operator-controller  Failed to update resource maroonedpods-validator, ValidatingWebhookConfiguration.admissionregistration.k8s.io "maroonedpods-validator" is invalid: webhooks[0].name: Invalid value: "maroonedpods.validator": should be a domain with at least three segments separated by dots

@Barakmor1 any chance you know what is that?