GDPR compliance in a K8S cluster for individual services

Posted August 24, 2020 555 views

I know that it’s best practice to host each client’s app/service/website on its private servers, to mitigate possible GDPR investigation caused downtimes.

But does anybody know how would this translate to a K8S architecture? How and where would it be best to separate client’s apps/services/websites to ensure that if the investigator needs access to verify certain GDPR complaints, will only receive access just to what it needs to and won’t affect any other running appliances?

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Submit an Answer
1 answer

Hi there @w0rldart,

I’m not a GDPR expert but I think that the following 2 solutions should be sufficient:

  • Host each customer on a separate Kubernetes cluster - this might be overkill for some apps.

  • Use one Kubernetes cluster but create separate namespaces, that way each application will be isolated in its own namespace. That is kind of similar to how the shared hosting industry works with control panels like cPanel and etc. They have 1 server but all sites are isolated under different accounts.


  • Thanks Bobby! Will separating clients under different namespaces be the equivalent of using separate nodes per client?

    • Hi there @w0rldart,

      Yes, the Kubernetes namespaces are the fundamental parts of authorization in Kubernetes. However, of course, putting each application on different nodes would have good data and network isolations as the applications would be “physically” separated.