![]() ![]() Check out Bitnami docs and community sitesīitnami is an application packaging and publishing startup that was acquired by VMware in 2019.name: mealie # this will be the name of release as seen by HelmĬert-manager. Let’s also define a relationship between releases:Īs we did significant modifications to our helmfile.yaml over course of this post, here is the complete file for reference: Now finaly, we can change the DB_ENGINE environment variable and add additional PG connection string variables to our primary release. For production, please see that you use the secret store. Word of caution! For the sake of simplicity, passwords in this example are kept as plain text in the deployment file. Then, let’s create new release for our pg database # Here we define all the Helm repositories used within this helmfile Sure we could, in theory, deploy PostgreSQL with our kubedeploy, but since there are more specialized charts, let’s not re-invent the wheel.įor this purpose, we will use Bitnami’s PostgreSQL chart Let’s see what we need to do to have this configured.įirst, let’s add PostgreSQL helm chart repository to our helmfile.yaml. For example, Mealie can also use PostgreSQL as its database type instead of SQLite. By using helmfile we can combine multiple applications and form dependencies. Kubectl port-forward service/mealie-kubedeploy 8091:80Īs I mentioned, kubedeploy is intended to be used with single-container applications. We still don’t have this service exposed to the public, but we can verify by doing a simple port forward: Our port should now be exposed, and our service object should accept traffic. Or you can even define your own probes and target URL’s, for example:įor now, we will stick to automatically created health check probes and deploy our configuration If you don’t wish to add health check probes, you can disable them by configuring health check.enabled = false within the values Keen observer might notice that once we define http port for our container, the chart will automatically add liveness and readiness probe for this container. Helmfile diff subcommand will use helm-diff plugin to display what would change To configure environment variables for container, we use: Since we named our port http there is an automatic service object definition within the chart that will target this port and listen on ClusterIP on port 80. The first thing we need to do is add an exposed port for our container in helmfile.yaml Mealie is now deployed in the cluster it’s time to configure its runtime via environment variables and expose its port so we can access it. Without further ado, let’s explore some of the use cases and capabilities of Kubedeploy. However, it can be a great starting point for developing your own chart based on it. This chart is by no means here to replace any complex deployment scenarios. ![]() Kubedeploy’s primary mission remained the same: simplify deploying single-container applications into Kubernetes clusters. With their valuable feedback, we extended the chart’s functionality to cover many other use cases we didn’t initially require. Soon we onboarded a few of our clients who started using this same chart. Over time as requirements grew, we evolved the chart to cover more and more use cases. You should be able to modify any application-specific configuration by changing the chart parameters via values.yaml ![]() At that point, we started working on the Kubedeploy Helm chart that would ease up deploying new applications while eliminating the need to maintain multiple charts per application. Most of the applications had same requirements and maintaining multiple charts for each application didn’t make any sense. Soon we realized there is a repeating pattern when deploying single-container applications. ![]() Initially, we started out writing Helm charts for every application. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |