Storage
organisations to deploy databases within Kubernetes instead of relying on external cloud providers. “One way to think about it is like AWS RDS, but instead of running on cloud infrastructure, KubeDB enables databases to run as containers inside Kubernetes,” Saha explains. KubeDB supports database provisioning and operational
scaling, ensuring enterprises can automate deployment, version control, and lifecycle management for stateful applications. By integrating Kubernetes operators, KubeDB automates complex database administration processes that Kubernetes alone does not support. “Kubernetes has the concept of an operator; you can write
custom code to manage databases, and that’s what KubeDB does,” Saha says. Operators provide standardised formats for database provisioning, ensuring consistent deployment methods. Storage compatibility is a crucial aspect of database operations, and KubeDB supports multiple storage options through CSI drivers, allowing businesses to work with both durable and ephemeral storage models. “On the cloud, you can use any standard storage. In this case, it’s durable storage, but we also support ephemeral options.” KubeDB supports Postgres up to version 17, providing organisations
with greater flexibility in database management. “Users can specify their preferred version,” Saha says. Scalability is a key feature of KubeDB, with the system allowing both horizontal and vertical scaling to meet workload demands. “You might start with three replicas and increase to five, or allocate more CPU and memory.” Security remains a priority, particularly for enterprises operating
within air-gapped environments that require robust infrastructure protections. KubeDB integrates with private registries, enabling organisations to manage deployments securely without external internet access. “If someone has an air-gapped cluster, they can point our product to their private registry, and it will pull images as needed,” Saha says. Te company’s backup and recovery solution, KubeStash,
integrates with Kubernetes environments to support full backups and disk-based recovery. It is compatible with cloud storage providers including Google Cloud, Azure Block Storage, and S3- compatible platforms. “Our system is designed to leverage existing storage solutions,
allowing users to store backups in Google Cloud, Azure Block Storage, and S3-compatible platforms,” Saha says. KubeStash also facilitates cross-cloud migration, enabling unrestricted data transfers between cloud environments. “Some cloud providers restrict snapshots within the same region,” Saha explains. “But our system allows full portability; you can back up data in AWS and restore it in Google Cloud seamlessly.” Voyager, introduced by Saha as a key traffic management
solution, optimises network communication across various database protocols. Te system assigns an IP address for external connections while enabling internal services to operate within the Kubernetes cluster. “Tis is an onboard gateway,” he says. “If you go to the in- cluster option, you’re pointing to a service name, but if you’re coming from outside, the system assigns an IP address, which you can then connect to.” Voyager simplifies cross-cluster database access, ensuring
compatibility with SQL Server, Oracle, and other protocols requiring
www.pcr-online.biz
additional encryption mechanisms. “Most databases use custom TCP-based protocols such as SQL Server or Oracle, and securing those with TLS encryption isn’t straightforward. Kubernetes doesn’t handle that out of the box,” Saha notes. Te challenges of secure database access are further mitigated
through KubeVault, an operator designed for secret and user management. It allows organisations to control user authentication with minimal manual oversight. “KubeVault helps store database secrets and set up user accounts with restricted functions,” Saha explains. “We integrate with HashiCorp KubeVault to ensure credentials are securely managed.” Te combined capabilities of Voyager and KubeVault allow
organisations to modernise their infrastructure while maintaining robust security. “We see a lot of activity in the on-prem space, with organisations modernising their infrastructure,” Saha says. Te company’s database management solutions are complemented
by a web-based UI, allowing users to oversee provisioning, scaling, and backups within a single interface. Te UI enables efficient interaction with Kubernetes-hosted databases, eliminating the complexity associated with direct container management. Security features are crucial to the company’s Kubernetes-
native approach, with TLS certificate management ensuring encrypted database access. “TLS management is important,” Saha says. Alongside Postgres, KubeStash supports Redis, providing equivalent backup and monitoring functionality. To enhance Kubernetes-native database management workflows, KubeStash integrates with GitOps automation tools, supporting microservices- based deployments and improving consistency. KubeStash is designed to deliver a flexible, scalable, and secure
framework for enterprise backup and recovery, prioritising storage efficiency, migration capabilities, and security. “Users want simplicity, reliability, and control, and that’s exactly what we provide,” Saha says. KubeStash incorporates strategies for memory optimisation and Spot Instance usage to reduce costs and ensure minimal resource wastage. AppsCode continues refining its integrations to ensure
scalability, vendor compatibility, and multi-tenancy. Future developments will focus on expanding virtual cluster support, improving observability, and enhancing AI-powered database automation. Te company’s strategic direction remains centred on providing Kubernetes-native solutions that effectively address enterprise database management challenges.
May/June 2025 | 37
Page 1 |
Page 2 |
Page 3 |
Page 4 |
Page 5 |
Page 6 |
Page 7 |
Page 8 |
Page 9 |
Page 10 |
Page 11 |
Page 12 |
Page 13 |
Page 14 |
Page 15 |
Page 16 |
Page 17 |
Page 18 |
Page 19 |
Page 20 |
Page 21 |
Page 22 |
Page 23 |
Page 24 |
Page 25 |
Page 26 |
Page 27 |
Page 28 |
Page 29 |
Page 30 |
Page 31 |
Page 32 |
Page 33 |
Page 34 |
Page 35 |
Page 36 |
Page 37 |
Page 38 |
Page 39 |
Page 40 |
Page 41 |
Page 42 |
Page 43 |
Page 44 |
Page 45 |
Page 46 |
Page 47 |
Page 48 |
Page 49 |
Page 50 |
Page 51 |
Page 52
