Use Cases for 915 Mizar Integration

Setup

1. Bring up a multi-node Arktos Cluster.
2. Install Arktos network CRD: "kubectl create -f ArktosNetwork.yaml".
3. Install Mizar CRD & operators: "kubectl create -f Mizar.yaml".

Case #1: Default & Non-Default network

Steps	Expected Result
kubectl create tenant T1	A "default" network is created and ready for use
kubectl create vpc demo; kubectl create -f demoNetwork.yaml (with the VPC ID) --tenant T1	A "demo" network is created and ready for use
kubectl delete network demo	The "demo" network is deleted (? Pending decision)

How to check a network is ready:

1. Its "status" is "ready"
2. Per-network "kube-DNS" service is created.
3. Per-network DNS deployment is created.

Case #2: Pod Connectivity

Steps	Expected Result
kubectl create -f pod1.yaml	pod1 is running, IP assigned
kubectl create -f pod2.yaml with a same node selector to pod1	pod2 is running, IP assigned, and able to communicate with pod1
kubectl create -f pod3.yaml with a different node selector to pod1	pod3 is running, IP assigned, and able to communicate with pod1 and pod2

For all cases, also verify:

• Pod IP is assigned from the specified subnet.
• Pod "readiness" and other annotations are correctly updated.

Case #3: Service Connectivity

Steps	Expected Result
kubectl create -f deployment1, service1.yaml	service1 is assigned an IP from the clusterIP range in network object
Access the cluster IP from a node or from a pod	the cluster IP is accessible
Kubectl scale deployment1	verify the pod IP list is correctly updated for the cluster IP
Kubectl delete deployment1, service1	Deletion succeed, and all endpoints are deleted on Mizar side as well

(TBD: do we only support clusterIP type of services?)

Case #4: Network Isolation

Steps	Expected Result
kubectl create -f pod1.yaml	pod1 is running, IP assigned
kubectl create -f pod2.yaml with a different network	pod2 is running, IP assigned, but not able to communicate with pod1