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

...

When the code was deployed the result was as below 


default goodly-squid-vnfsdk-556f59ccd9-jx9q8 1/1 Running 0 32s 10.42.81.107 k8s-4
default goodly-squid-vnfsdk-556f59ccd9-n95jh 1/1 Running 0 32s 10.42.73.55 k8s-2
default goodly-squid-vnfsdk-556f59ccd9-snlzc 1/1 Running 0 32s 10.42.233.242 k8s-3
default goodly-squid-vnfsdk-556f59ccd9-xtzff 1/1 Running 0 32s 10.42.129.25 k8s-1
default goodly-squid-vnfsdk-postgres-78d58775c4-98dr9 1/1 Running 0 32s 10.42.130.80 k8s-4
default goodly-squid-vnfsdk-postgres-78d58775c4-9cf5g 1/1 Running 0 32s 10.42.222.207 k8s-3
default goodly-squid-vnfsdk-postgres-78d58775c4-9rnhh 1/1 Running 0 32s 10.42.50.224 k8s-1
default goodly-squid-vnfsdk-postgres-78d58775c4-s4l8r 1/1 Running 0 32s 10.42.49.238 k8s-2Image Added


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.

...