Tips, Expertise, Articles and Advice from the Pro's for Your Website or Blog to Succeed
Want to learn about deploying CockroachDB on Azure Kubernetes Service? We do not officially publish such documentation, so this article is an attempt to do just that.
There are certain differences in operating Kubernetes on Azure. For more information, please refer to their docs.
Velero is an open source tool to safely back up and restore, perform disaster recovery, and migrate Kubernetes cluster resources and persistent volumes
Velero consists of:
Welcome to part four of this blog series! So far, we have a Kafka single-node cluster with TLS encryption on top of which we configured different authentication modes (TLS and SASL SCRAM-SHA-512), defined users with the User Operator, connected to the cluster using CLI and Go clients, and saw how easy it is to manage Kafka topics with the Topic Operator. So far, our cluster used ephemeral persistence, which in the case of a single-node cluster, means that we will lose data if the Kafka or Zookeeper nodes (Pods) are restarted due to any reason.
Let's march on! In this part we will cover:
Today, we are deploying a Kubernetes cluster for our application. Azure Kubernetes Service (AKS) has many advantages over similar Kubernetes platforms because the user does not pay for the master VMS or its maintenance. An Azure subscriber pays only for the worker VMS. However, AKS — out of the box — is not a production-ready product. The following are the steps we need to take before we became almost production-ready.
In this article, we are going to discuss the following topics: