@hashicorp
The Helm plugin deploys to Kubernetes from a Helm chart. The Helm chart can be a local path or a chart in a repository.
- Official
- Built-in
Updated last year
- GitHub(opens in new tab)
Helm Platform
Archive Notice
This integration relates to a legacy version of Waypoint and is no longer actively maintained.Deploy to Kubernetes from a Helm chart. The Helm chart can be a local path or a chart in a repository.
Entrypoint Functionality
Waypoint entrypoint functionality such as logs, exec, app configuration, and more require two properties to be true:
The running image must already have the Waypoint entrypoint installed and configured as the entrypoint. This should happen in the build stage.
Proper environment variables must be set so the entrypoint knows how to communicate to the Waypoint server. This step happens in this deployment stage.
Step 2 does not happen automatically. You must manually set the entrypoint environment variables using the templating feature. These must be passed in using Helm values (i.e. the chart must make environment variables configurable).
This is documented in more detail with a full example in the Kubernetes Helm Deployment documentation.
URL Service
If you want your workload to be accessible by the Waypoint URL service, you must set the PORT environment variable within the pod with your web service and also be using the Waypoint entrypoint (documented in the previous section).
The PORT environment variable should be the port that your web service is listening on that the URL service will connect to. See one of the examples below for more details.
Interface
- Input: None
- Output: k8s_helm.Deployment
Examples
Parameters
13 Results
set
Requiredlist of struct { Name string "hcl:\"name,attr\""; Value string "hcl:\"value,attr\""; Type string "hcl:\"type,optional\"" }A single value to set. This can be repeated multiple times. This sets a single value. Separate nested values with a
.
. This is the same as the--set
flag onhelm install
.