Use CloudCasa With Azure Kubernetes Service
CloudCasa by Catalogic announced the integration with Azure Kubernetes Service (AKS) at KubeCon in Valencia and it has so far received positive feedback from customers. In this episode of TFiR Let’s Talk, Swapnil Bhartiya sits down with Sathya Sankaran, Founder and General Manager, CloudCasa by Catalogic and Sebastian Głąb, CloudCasa Architect, as they give a demo and explain the key reasons to use CloudCasa to protect AKS Applications.
Key highlights from this video interview are:
- Awareness is key when protecting workloads running under certain managed services. Having AKS integration means you can capture information on how the cluster is configured allowing you to restore information quickly. Sankaran explains that credential storing is dangerous so they introduced the ability to connect to Azure through Azure Resource Manager (ARM) templates.
- Glab shares the top reasons why ARM integration is better, firstly, they do not ask users to generate any access or secret keys since you should not store credentials. ARM integration means that after integration with the Azure account with CloudCasa, they can automatically discover all the AKS clusters and resource groups within the Azure account. Thirdly, ARM integration gives you more control of your account.
- The AKS integration means users can see all the clusters they have installed and running in their Azure clusters so if they need to bring back data quickly, they can. They can add multiple Azure accounts for centralized visibility into all their cloud accounts and all the clusters in those accounts so they can choose which workloads to protect to help with compliance.
- Sankaran explains that the AKS integration with CloudCasa also helps with data protection and backup for insurance purposes. He discusses how the CSI standard for Kubernetes only supports snapshots but doesn’t help restore Azure files. Sankaran feels that this is where CloudCasa solves this problem.
- Privacy is an important factor when protecting data, so to tackle this CloudCasa’s backup data is encrypted end to end. Sankaran explains that it is possible to send the data from the Azure infrastructure to an Azure storage using the Azure backbone and bypassing the public internet.
- Glab demonstrates how they spin up the cluster and do recovery as code without intervention from the user. He explains that they can also do across account restore and how it works.
- Sankaran shares some final insights into the benefits of CloudCasa explaining that they automatically update the user’s agents, and maintain a backup infrastructure. He explains that they support a multi-tenancy option and can enable multi-tenancy self-service backup and restore.
Give CloudCasa a try and sign up for our Free Plan (no credit card necessary).
Top 10 Reasons for Using CloudCasa
Immediately benefit from a powerful and easy to use Kubernetes backup service that does all the hard work for you to backup your multi-cluster applications and provide granular or cluster-level recovery including cross-account, cross-cluster, and cross-cloud recovery.
CloudCasa is so easy to use that even developers won’t mind managing backups. It comes with a generous free service plan (no credit card required) and it is a great alternative to using Velero or Kasten.
Here are the Top 10 reasons to use CloudCasa for Kubernetes backup, migration and disaster recovery, vs. these options:
- Do-it-yourself (DIY) products, whether open source like Velero or a product that you have to license, install and maintain like Kasten or Trilio
- Retrofitted enterprise or cloud backup products with container support, that still have all their baggage from the past (you know who they are)
- Cloud vendor or any VM backup that is not Kubernetes aware, or is single cloud only
- Container storage solutions with replication, or that come bundled with a single purpose backup application like PX-backup
- Solutions that don’t offer a free service plan or that charge by the cluster or by worker nodes