well-known/charts/well-known
semantic-release-bot 25e69d3f24 chore(release): 1.7.2
## [1.7.2](https://github.com/stenic/well-known/compare/v1.7.1...v1.7.2) (2023-11-10)

### Bug Fixes

* Update dependecies ([2b9f064](2b9f064f03))
* Update nginx image ([bc5285c](bc5285c694))
2023-11-10 08:32:42 +00:00
..
ci fix: kubescape 2023-03-12 01:21:04 +01:00
templates fix(helm): Security fixes - netpol 2023-10-28 00:18:22 +02:00
.helmignore feat: Init poc 2023-03-11 20:58:56 +01:00
Chart.yaml chore(release): 1.7.2 2023-11-10 08:32:42 +00:00
README.md fix: Add tmpl in correct location 2023-04-11 10:39:14 +02:00
README.md.gotmpl fix: Add tmpl in correct location 2023-04-11 10:39:14 +02:00
values.yaml fix: Update nginx image 2023-11-10 09:22:09 +01:00

well-known

TL;DR;

helm repo add k8status https://stenic.github.io/well-known/
helm install well-known --namespace well-known well-known/well-known

Introduction

This chart installs well-known on a Kubernetes cluster using the Helm package manager.

Prerequisites

  • Kubernetes 1.18+
  • Helm 3.0+

Installing the Chart

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

helm repo add well-known https://stenic.github.io/well-known/
helm install well-known --namespace well-known well-known/well-known

These commands deploy well-known on the Kubernetes cluster in the default configuration. The Parameters section lists the parameters that can be configured during installation.

Tip: List all releases using helm list

Uninstalling the Chart

To uninstall/delete the my-release deployment:

helm delete my-release

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

Configuration

The following tables list the configurable parameters of the well-known chart and their default values.

Key Type Default Description
affinity object {}
autoscaling.enabled bool false
autoscaling.maxReplicas int 100
autoscaling.minReplicas int 1
autoscaling.targetCPUUtilizationPercentage int 80
fullnameOverride string ""
image.pullPolicy string "Always"
image.repository string "ghcr.io/stenic/well-known"
image.tag string ""
imagePullSecrets list []
ingress.annotations object {}
ingress.className string ""
ingress.enabled bool false
ingress.hosts[0].host string "chart-example.local"
ingress.hosts[0].paths[0].path string "/.well-known/"
ingress.hosts[0].paths[0].pathType string "ImplementationSpecific"
ingress.tls list []
nameOverride string ""
networkpolicies.enabled bool false
networkpolicies.kubeApiServerCIDR string "<IP>/32"
nodeSelector object {}
podAnnotations object {}
podSecurityContext object {}
replicaCount int 2
resources.limits.cpu string "50m"
resources.limits.memory string "64Mi"
resources.requests.cpu string "20m"
resources.requests.memory string "32Mi"
securityContext.allowPrivilegeEscalation bool false
securityContext.capabilities.drop[0] string "ALL"
securityContext.readOnlyRootFilesystem bool true
securityContext.runAsNonRoot bool true
service.port int 80
service.type string "ClusterIP"
serviceAccount.annotations object {}
serviceAccount.create bool true
serviceAccount.name string ""
tolerations list []
webserver.image.pullPolicy string "Always"
webserver.image.repository string "nginxinc/nginx-unprivileged"
webserver.image.tag string "1.23"
webserver.resources.limits.cpu string "50m"
webserver.resources.limits.memory string "24Mi"
webserver.resources.requests.cpu string "10m"
webserver.resources.requests.memory string "10Mi"

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

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

helm install my-release -f values.yaml well-known/well-known