By w0rldart
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?
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
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.
Regards, Bobby
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and SMBs
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.