This article is the first in a two-part article series on Kubernetes configuration patterns, which represent ways of configuring Kubernetes applications and controllers. Part 1 introduces simple approaches that use only Kubernetes primitives. These patterns are applicable to any application running on Kubernetes. Part 2 will introduce more advanced patterns. These patterns require you to code against the Kubernetes API when you are developing Kubernetes controllers.
Continue reading Kubernetes configuration patterns, Part 1: Patterns for Kubernetes primitives
So, you wrote your Quarkus application, and now you want to deploy it to a Kubernetes cluster. Good news: Deploying a Quarkus application to a Kubernetes cluster is easy. Before you do this, though, you need to straighten out your application’s properties. After all, your app probably has to connect with a database, call other services, and so on. These settings are already defined in your
application.properties file, but the values match the ones for your local environment and won’t work once deployed onto your cluster.
So, how do you easily solve this problem? Let’s walk through an example.
Continue reading “Using Kubernetes ConfigMaps to define your Quarkus application’s properties”
ConfigMaps is the Kubernetes counterpart of the Spring Boot externalized configuration. ConfigMaps is a simple key/value store, which can store simple values to files. In this post “Configuring Spring Boot on Kubernetes with ConfigMap”, we will see how to use ConfigMaps to externalize the application configuration.
Continue reading “Configuring Spring Boot on Kubernetes with ConfigMap”