a7da4dbb38
* chore(deps): update helm chart common to v4.3.0 * Remove CHANGELOG templates Co-authored-by: Renovate Bot <bot@renovateapp.com> Co-authored-by: Bᴇʀɴᴅ Sᴄʜᴏʀɢᴇʀs <me@bjw-s.dev> |
||
---|---|---|
.. | ||
ci | ||
templates | ||
.helmignore | ||
Chart.yaml | ||
README_CONFIG.md.gotmpl | ||
README.md | ||
README.md.gotmpl | ||
values.yaml |
piaware
Program for forwarding ADS-B data to FlightAware
This chart is not maintained by the upstream project and any issues with the chart should be raised here
Source Code
Requirements
Kubernetes: >=1.16.0-0
Dependencies
Repository | Name | Version |
---|---|---|
https://library-charts.k8s-at-home.com | common | 4.3.0 |
TL;DR
helm repo add k8s-at-home https://k8s-at-home.com/charts/
helm repo update
helm install piaware k8s-at-home/piaware
Installing the Chart
To install the chart with the release name piaware
helm install piaware k8s-at-home/piaware
Uninstalling the Chart
To uninstall the piaware
deployment
helm uninstall piaware
The command removes all the Kubernetes components associated with the chart including persistent volumes and deletes the release.
Configuration
Read through the values.yaml file. It has several commented out suggested values. Other values may be used from the values.yaml from the common library.
Specify each parameter using the --set key=value[,key=value]
argument to helm install
.
helm install piaware \
--set env.TZ="America/New York" \
k8s-at-home/piaware
Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart.
helm install piaware k8s-at-home/piaware -f values.yaml
Custom configuration
IMPORTANT NOTE: a piaware device must be accessible on the node where this pod runs, in order for this chart to function properly.
First, you will need to mount your piaware device into the pod, you can do so by adding the following to your values:
additionalVolumeMounts:
- name: usb
mountPath: /path/to/device
additionalVolumes:
- name: usb
hostPath:
path: /path/to/device
Second you will need to set a nodeAffinity rule, for example:
affinity:
nodeAffinity:
requiredDuringSchedulingIgnoredDuringExecution:
nodeSelectorTerms:
- matchExpressions:
- key: app
operator: In
values:
- piaware
... where a node with an attached piaware USB device is labeled with app: piaware
Values
Important: When deploying an application Helm chart you can add more values from our common library chart here
Key | Type | Default | Description |
---|---|---|---|
affinity | object | {} |
Affinity constraint rules to place the Pod on a specific node. [ref] |
env | object | See below | environment variables. See application docs for more details. |
env.TZ | string | "UTC" |
Set the container timezone |
image.pullPolicy | string | "IfNotPresent" |
image pull policy |
image.repository | string | "mikenye/piaware" |
image repository |
image.tag | string | "v5.0" |
image tag |
ingress.main | object | See values.yaml | Enable and configure ingress settings for the chart under this key. |
persistence | object | See values.yaml | Configure persistence settings for the chart under this key. |
persistence.usb | object | See values.yaml | Configure a hostPathMount to mount a USB device in the container. |
securityContext.privileged | bool | true |
(bool) Privileged securityContext may be required if USB device is accessed directly through the host machine |
service | object | See values.yaml | Configures service settings for the chart. |
Changelog
Version 8.2.0
Added
N/A
Changed
- Upgraded
common
chart dependency to version4.3.0
.
Fixed
N/A
Older versions
A historical overview of changes can be found on ArtifactHUB
Support
Autogenerated from chart metadata using helm-docs v0.1.1