Originally published on the Bitnami Engineering Portal, by Angus Lees.
At Bitnami, we have been using Kubernetes internally, and publishing applications targeting Kubernetes (such as Kubeapps!) for a few years now. Over that time, we have seen a recurring “gap” in the ecosystem from both directions:
I am Adnan Abdulhussein, a co-chair of Kubernetes SIG Apps (along with the brilliant Matt Farina and Kenneth Owens), and I’m going to explain a little bit about how you can get involved in the Kubernetes community. If you’re interested in learning more, I’d love to meet you in-person at KubeCon!
Special Interest Groups in Kubernetes provide places for the community to focus development and discussion on a particular part of the project. SIG Apps is one of several such groups, which is focused on deploying and operating applications in Kubernetes. The group is typically made up of cluster operators…
A couple of months ago, Bitnami and Microsoft launched support for the Kubernetes Service Catalog in Kubeapps. Today, with general availability of Azure Kubernetes Service, we are excited to unveil some upcoming changes to Kubeapps and the Service Catalog that make working with Azure cloud services a breeze.
Kubeapps is a Kubernetes dashboard that supercharges your Kubernetes cluster with simple browse and click deployment of applications. Building on Bitnami’s contributions to leading open source projects, Kubeapps provides a complete application delivery environment that empowers users to launch, review and share applications.
Monocular, is an open source search and discovery front-end for Helm Chart repositories. You can see it in action over at https://kubeapps.com, but running it in your own cluster gives you a neat way to create and manage Helm Chart installations inside your cluster. Let’s take a look at running it on an OpenShift cluster.
Before we install Monocular, we need to install Helm on OpenShift. More specifically, we need to run Helm’s server-side component, Tiller. This runs in the
kube-system namespace and uses the Kubernetes API to create and manage the resources defined by charts.
The Service Catalog provides a way for developers, ISVs, and SaaS vendors to provision instances of services that can be consumed by applications in a standard way. Originally designed for the CloudFoundry platform, the Open Service Broker project was recently founded to standardise the specification and open it up to other platforms such as Kubernetes and OpenShift. The Kubernetes Special Interest Group for Service Catalog has been working on integrating the Open Service Broker API with the Kubernetes ecosystem.
Using the Service Catalog, an application developer has the ability to request services from a catalog without worrying about how and…