Back to Charts

⚠️ Repo Archive Notice

stable/satisfy/README.md

latest3.7 KB
Original Source

⚠️ Repo Archive Notice

As of Nov 13, 2020, charts in this repo will no longer be updated. For more information, see the Helm Charts Deprecation and Archive Notice, and Update.

Satisfy Helm Chart

DEPRECATION NOTICE

This chart is deprecated and no longer supported.

Installing the Chart

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

console
$ helm install --name my-release stable/satisfy

Uninstalling the Chart

To uninstall/delete the my-release deployment:

console
$ helm delete my-release

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

Configuration

ParameterDescriptionDefault
image.pullPolicyImage pull policyAlways
image.repositoryImage repositorydocker.io/anapsix/satisfy
image.tagImage tagv3.0.4
image.digestImage digestsha256:fae78e3809e9d08990c7d7d6699a734f7e584c28ce49381a1a699e1694481ab8
image.pullSecretsSpecify image pull secrets[]
service.typeType of serviceClusterIP
service.portService port80
ingress.enabledEnables Ingressfalse
ingress.annotationsIngress annotations{}
ingress.labelsIngress labels[]
ingress.hostsIngress accepted hostnames[]
ingress.tlsIngress TLS configuration[]
terminationGracePeriodSecondsTermination grace period (in seconds)15
livenessProbe.enabledEnables LivenessProbetrue
readinessProbe.enabledEnables readinessProbetrue
affinityNode/pod affinities{}
nodeSelectorNode labels for pod assignment{}
resourcesPod resource requests & limits{}
tolerationsList of node taints to tolerate[]
persistence.enabledUse a PVC to persist datatrue
persistence.existingClaimUse an existing PVC to persist datanil
persistence.storageClassStorage class of backing PVCnil
persistence.accessModeUse volume as ReadOnly or ReadWriteReadWriteOnce
persistence.sizeSize of data volume8Gi
satisfy.repoNameSatis repository namemyrepo
satisfy.homepageSatis repository URLhttp://composer.local
satisfy.sshPrivateKeySSH Private key used with GIT reposnil

When both image.tag and image.digest are present, image.digest will be used. See Docker docs for more details about using image digest.

FQDN to access the service should be used as satisfy.homepage value, whether via Ingress, or LoadBalancer-type service with DNS records matching satisfy.homepage, or some other method.