Creating an Internal GKE Ingress for Kasten
GKE provides a high-performance solution for load balancing containers. But how do you expose an internal ingress in this architecture? More specifically, how do you expose an internal ingress for Kasten?
Demos, videos, how-tos, and general ramblings.
GKE provides a high-performance solution for load balancing containers. But how do you expose an internal ingress in this architecture? More specifically, how do you expose an internal ingress for Kasten?
When Kasten need to interact with a cloud provider API as Azure we have 2 approaches. One approach is to store the credential of a service principal in a secret but another one is to use federated identity. Federated identity avoid storing credential in a secret and bring much better security. Let's see how it works.
Kasten now officially supports SUSE Virtualization (previously known as SUSE Harvester)
In this post, we take a look at the recently published Veeam Kasten Red Hat OpenShift Virtualization Reference Architecture
With csi snapshots backing up with Kasten is very simple. Since april 2024 the azure file csi driver now support snapshot (for SMB volume) and is shipped with AKS. Let's see how easy it is now to backup an azure file volume in Kubernetes.
The rule of thumb in the backup world is to always have a copy of your backup in another site. Doing snapshot is not enough, you need to copy this snapshot somewhere else. But when you are on Azure this operation can be done very efficiently by leveraging the Azure capabilities to copy your snapshot to another region. This can improve dramatically your RPO and your RTO. Let's see how it works with Kasten.