{"id":32478,"date":"2021-01-11T14:40:24","date_gmt":"2021-01-11T14:40:24","guid":{"rendered":"https:\/\/www.commvault.com\/?p=32478"},"modified":"2023-12-27T11:02:11","modified_gmt":"2023-12-27T16:02:11","slug":"all-your-questions-answered","status":"publish","type":"post","link":"https:\/\/www.commvault.com\/blogs\/all-your-questions-answered","title":{"rendered":"All Your Questions Answered"},"content":{"rendered":"\n
By Mark Jow<\/p>\n\n\n\n
During December\u2019s EMEA Commvault Virtual Connections, I was struck by how much it felt like an in-person conference. We had so much great engagement with customers and experts\u2014it was so great to interact with so many people on the hot customer topics of cloud, containers and of course ransomware.<\/p>\n\n\n\n
Unfortunately, as with all good events, we didn\u2019t have time to get to everyone\u2019s questions. Still, we wanted to make sure that you got the Commvault answers you need to make the most of your data. Below, check out answers from our team of Commvault experts to your questions.<\/p>\n\n\n\n
CUSTOMER: <\/strong><\/p>\n\n\n\n When Commvault talk about protecting Kubernetes, is it the containers and storage? Or can Commvault backup the registry, the namespace configuration, ingress configuration? Also, is there a way to collect\/protect the STDOUT\/STDERR from Kubernetes? Will you backup that as well when you protect the container? <\/strong><\/p>\n\n\n\n Marek Kedzierski, Senior Sales Engineer, Commvault:<\/em><\/p>\n\n\n\n Commvault\u2019s agent for Kubernetes can protect both applications and persistent volumes. An application can be a pod, deployment, stateful set or workload. Our agent automatically protects all resources associated with an application, such as secrets and configmaps. Our persistent volume backup process uses CSI Snapshots. Therefore, our recommendation is to deploy our agent in Kubernetes clusters where persistent volumes are provisioned with storage class backed by the CSI driver. <\/p>\n\n\n\n Container registries, namespace and ingress configuration, STDOUT\/STDERR generated by pods are currently not supported by our agent. However, our agent is actively updated, and these resources may be protected in the future (of course, no guarantees).<\/p>\n\n\n\n