k8s-at-home/searx

Chart version: 1.1.1
Api version: v2
App version: 0.18.0
Searx is a privacy-respecting, hackable metasearch engine
application
Chart Type
Active
Status
Unknown
License
160
Downloads
https://k8s-at-home.com/charts
Set me up:
helm repo add center https://repo.chartcenter.io
Install Chart:
helm install searx center/k8s-at-home/searx
Versions (0)

Searx

This is a helm chart for Searx.

This chart is not maintained by the upstream project and any issues with the chart should be raised here

TL;DR;

$ helm repo add k8s-at-home https://k8s-at-home.com/charts/
$ helm install k8s-at-home/searx

Configuration

The following table lists the configurable parameters of the nextcloud chart and their default values that have to be overriden.

Parameter Description Default
searx.baseUrl external url https://serax.DOMAIN
searx.mortyKey Morty reverse proxy unique key changeme

Installing the Chart

To install the chart with the release name my-release:

helm install --name my-release k8s-at-home/searx

Uninstalling the Chart

To uninstall/delete the my-release deployment:

helm delete my-release --purge

The command removes all the Kubernetes components associated with the chart and deletes the release.

Configuration

Read through the charts values.yaml file. It has several commented out suggested values. Additionally you can take a look at the common library values.yaml for more (advanced) configuration options.

Specify each parameter using the --set key=value[,key=value] argument to helm install. For example,

helm install searx \
  --set env.TZ="America/New_York" \
    k8s-at-home/searx

Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example,

helm install searx k8s-at-home/searx --values values.yaml
image:
  tag: ...

NOTE

If you get

Error: rendered manifests contain a resource that already exists. Unable to continue with install: existing resource conflict: ...`

it may be because you uninstalled the chart with skipuninstall enabled, you need to manually delete the pvc or use existingClaim.


Upgrading an existing Release to a new major version

A major chart version change (like 1.0.1 -> 2.0.0) indicates that there is an incompatible breaking change potentially needing manual actions.