Ensure your Database Performance on Kubernetes using KubeDB. KubeDB provides a bunch of features that increase your database performance on Kubernetes.
$ helm repo add appscode https://charts.appscode.com/stable/ $ helm repo update $ helm install kubedb appscode/kubedb \ --version v2023.08.18 \ --namespace kubedb --create-namespace \ --set kubedb-provisioner.enabled=true \ --set kubedb-ops-manager.enabled=true \ --set kubedb-autoscaler.enabled=true \ --set kubedb-dashboard.enabled=true \ --set kubedb-schema-manager.enabled=true \ --set-file global.license=/path/to/the/license.txt
Kubernetes provides a powerful cloud agnostic storage abstraction that enables Kubernetes workloads to use a wide variety of block and file storage to persist data. KubeDB uses Persistent Volume Claims (PVC) to dynamically provision disks for database instances. Using appropriately defined StorageClasses, KubeDB provisioned database instances are designed to scale from small development workloads up to performance-intensive workloads on private and public cloud environments.
Cloud providers like AWS provide provisioned IOPS Storage which is an SSD-backed storage option designed to deliver fast, predictable, and consistent I/O performance. You specify an IOPS rate when creating a StorageClass, and KubeDB provisions disks at that IOPS rate for the lifetime of the database instance. This storage type is optimized for I/O-intensive transactional (OLTP) database workloads.
There is a growing ecosystem of cloud-native storage solutions like Rook (Ceph), OpenEBS, Portworx that provide network attached storage for containerized workloads. These systems can provide block storage via CSI drivers in cloud or bare metal clusters. KubeDB can provision database instances that utilize these storage systems using standard Kubernetes abstractions.
Most Kubernetes Storage systems enable remote storage which persists data independent of the Kubernetes node where the data originated. Remote storage usually can not offer the consistent high performance guarantees of local directly-attached storage. Using the Local Persistent Volume plugin, KubeDB can consume high performance local storage seamlessly. However, local volumes are still subject to the availability of the underlying node. HA database instances using local volumes are able to tolerate this reduced availability, as well as automatically recover from potential data loss, depending on the durability characteristics of the underlying disk.
KubeDB runs your database instances inside the same pod network as the workloads that use these database instances. Unlike database instances managed by DBaaS vendors, there is no cross VPC latency between your database instances and your applications.
Trusted by top engineers at the most ambitious companies
InterSystems was delighted to engage with AppsCode in the delicate, yet fundamental task of supporting durable, non-ephemeral workloads with Kubernetes. We needed the best-prepared, most-proficient database operator consulting in the industry. Given AppsCode's pedigree of database building operators, the decision was easy. No time was wasted and all objectives reached in an amazingly short period of time. I would recommend AppsCode consulting for any Kubernetes related work.
Voyager made it simple and efficient for us to protect and initiate our bare metal Kubernetes workload. Its underlying technology and extensive L4 support along with seamless SSL integration is what made us choose Voyager over others. Voyager team is also very responsive when it comes to support. Great product!
Voyager is the easiest way to use the fast and reliable HAProxy as our ingress controller. At PriceHubble, it is the corner-stone of our blue/green deployments.
I work with a few Kubernetes clusters and we use Voyager as our preferred ingress controller. We really like the ease of configuration. Documentation is pretty good. Also the use of HaProxy is important for us because it works really well with both L4 and L7 load balancing. One of our TCP services, Wayk Now, is able to withstand thousands of persistent connections very smoothly at the same time.
We really like using Voyager. Its straightforward and well-documented config and SSL (especially Let's Encrypt) has made our migration of services to Kubernetes a breeze. Each major version has been a very welcome update!
Here are a few of the questions we get the most. If you don't see what's on your mind, contact us anytime.
Yes, you can manage as many databases as you want within a single subscription to KubeDB, and there is no extra charge for that!
Yes, of course! KubeDB is platform-independent. You can use KubeDB in any cloud or on-premises.
KubeDB is running in production by multiple Governments and large organizations. Your data is always safe within KubeDB.
We offer 24x7 technical system and maintain SLA to provide 100% reliability to our customers.
Yes, Stash is seemingly integrated with KubeDB. There is no extra charge for using Stash. It is complimentary with KubeDB.
Of course! We offer a 30 days license free of cost to try all features of KubeDB Enterprise Edition.
Yes, you can seemlessly upgrade from the Community edition to the Enterprise Edition without any downtime.
There is no cancellation fee. But plans are subject to minimum duration (1 year) as stated above.
We prefer ACH transfer for US based customers and international wire transfer for everyone else. We can also accept all popular credit/debit cards such as Visa, Mastercard, American Express, Discover, etc.
KubeDB community edition is FREE to use on any supported Kubernetes engines. You can deploy and manage your database in Kubernetes using KubeDB. There is no up-front investment required. We offer a 30 days license FREE of cost to try KubeDB Enterprise edition.