Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Geo-Redundancy:-

Problem/Requirement:-

...

For achieving this we used a 4 node setup as shown below 


NAME      STATUS    ROLES     AGE       VERSION
k8s-1     Ready     <none>    44d       v1.10.5-rancher1
k8s-2     Ready     <none>    44d       v1.10.5-rancher1
k8s-3     Ready     <none>    43d       v1.10.5-rancher1
k8s-4     Ready     <none>    44d       v1.10.5-rancher1

And we used the default labels provided by kubernetes to each nodes 

kubectl get nodes --show-labels
NAME      STATUS    ROLES     AGE       VERSION            LABELS


AntiAffinity between DB Pods

Now lets see how the codes looks like for configuring the Anti-Affinity for VNFSDK-POSTGRESS PODs (just for the POC purpose we increased the replica count to 4)

...

This snippet of values.yaml  under vnfsdk-postgress dir  ensures that the db pods of vnfsdk-postgress will never reside on the same nodes

Affinity for DB and App pods and Antiaffinity for APP pods

Now for the Affinity between the DBand the APPpods and also the antiaffinity between APP pods we used the below code snippet in values.yaml of vnfsdk

...

When the code was deployed the result was as below 



Replica sets on different nodes with the APP and DB on the same node while the APP and DB are also never colocated on the same node

K8s-1k8s-2k8s-3k8s-4
goodly-squid-vnfsdk-556f59ccd9-xtzff goodly-squid-vnfsdk-556f59ccd9-n95jhgoodly-squid-vnfsdk-556f59ccd9-snlzc goodly-squid-vnfsdk-556f59ccd9-jx9q8
goodly-squid-vnfsdk-postgres-78d58775c4-9rnhhgoodly-squid-vnfsdk-postgres-78d58775c4-s4l8r goodly-squid-vnfsdk-postgres-78d58775c4-9cf5g goodly-squid-vnfsdk-postgres-78d58775c4-98dr9



So with this, We achieved a deployment Active-Active Geo-redundancy.

...