A: The Bitnami Kubernetes Production Runtime (BKPR) is a collection of services that make it easy to run production workloads in Kubernetes. The services are ready-to-run, and pre-integrated with each other so they work out of the box. They are based on best-of-breed popular projects such as Prometheus and Kibana, and cover logging, monitoring, DNS, certificate management and other common infrastructure needs.
A: At the time of writing, BKPR supports Azure Kubernetes Service (AKS), Google Kubernetes Engine (GKE) and Amazon Elastic Container Service for Kubernetes (EKS). Other Kubernetes platforms will be supported in future.
A: See the roadmap document. Generally work is prioritised based on perceived demand and effort, so open a GitHub issue or propose a PR directly if you want to influence this.
A: BKPR consists of a collection of Kubernetes manifests written in jsonnet plus the accompanying kubeprod binary which deals with all the platform-specific details, evaluates the jsonnet manifests, and applies them to the existing Kubernetes cluster.
A: Yes. BKPR only adds functionality to an existing Kubernetes cluster while keeping compatibility with other frameworks like Helm.
Q: How does BKPR differ from me deploying the needed components via e.g. Helm, where I can choose which components and configurations to use?
A: BKPR is an out-of-the-box, fully-tested, maintained, and integrated framework from Bitnami. All components, and their configurations, have been tested exhaustively to work on several Kubernetes platforms, such as Azure Kubernetes Service, Google Kubernetes Engine and Amazon Elastic Container Service for Kubernetes. Bitnami also follows these upstream components closely to deliver in-time security and bug fixes, freeing you from this burden.
A: BKPR is an open-source project, which also means that all contributions are welcome, either via code, documentation or by filing issues.
A: BKPR is an open-source project. Please read the LICENSE for additional information.
A: Bitnami-built Docker images follow upstream closely, with added continuous integration and testing, additional security best-practices (e.g. non-root containers), and a predictable release and support cycle.
A: It is advisable to be extremely cautious when uninstalling BKPR, especially if there are any workloads that depend on features enabled by BKPR. Examples of such services are automatic DNS registration and TLS certificate generation for HTTP-based Kubernetes Ingress resources.
Other features implemented by BKPR are not in the service path, like Elasticsearch, Kibana or Prometheus. Uninstalling these will impact the logging and monitoring services provided by BKPR. The underlying data storage for these services uses Kubernetes Persistent Volumes and uninstalling BKPR will not destroy them (they are preserved). If you later decide to re-install BKPR, the data will still be accessible.
A: Yes. kubeprod supports several Kubernetes platforms, like AKS and GKE. The first time kubeprod is run to install BKPR on any of these platforms, a JSON configuration file is generated which contains these platform-specific parameters, like the DNS domain/suffix used for automatic DNS management of Ingress resources, identifiers and secrets. This JSON configuration file is stored locally, in the current working directory as a file named kubeprod-autogen.json, and is required for subsequent runs of kubeprod.
A: Please refer to the BKPR upgrade section, in the workflow document.
A: Please refer to the BKPR upgrades and support document.
A: Follow the releases section in the GitHub project. The changelog for every release describes the bug fixes, security updates and new features.
A: When there are any issues or comments you want to report, please do report them by creating an issue in GitHub.