github/deprecated-helm-charts
1
0
Fork 0
mirror of https://github.com/helm/charts.git synced 2026-08-23 22:37:45 +00:00
Code Issues Packages Projects Releases Wiki Activity

Typo fix in unbound/README.md: "clusterip"&"cluster IP"->"ClusterIP" (#4919)

Browse Source 
* add version

add version

* Update README.md

ip->IP
clusterip->ClusterIP
cluster IP->ClusterIP
This commit is contained in:
AdamDang
2018-04-18 12:31:00 -07:00
committed by k8s-ci-robot
parent 8f352443a4
commit b820d6c85e
2 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
stable/unbound/Chart.yaml
+1 -1
View File
@@ -2,7 +2,7 @@ apiVersion: v1
description: Unbound is a fast caching DNS resolver
home: https://www.unbound.net/
name: unbound
version: 0.1.0
version: 0.1.1
appVersion: 1.6.7
sources:
- http://unbound.nlnetlabs.nl/svn/
stable/unbound/README.md
+3 -3
View File
@@ -4,7 +4,7 @@
## Configuration
The chart values file contains the default settings for the unbound server. In the default configuration unbound will allow queries from localhost only, and will not have any forward zones. This means that queries sent to the clusterip of the service will return access denied, and queries from localhost for anything other than the health check record `health.check.unbound` will return NXDOMAIN.
The chart values file contains the default settings for the unbound server. In the default configuration unbound will allow queries from localhost only, and will not have any forward zones. This means that queries sent to the ClusterIP of the service will return access denied, and queries from localhost for anything other than the health check record `health.check.unbound` will return NXDOMAIN.
You can configure unbound for your specific use case by passing a values file that contains the following properties. Most or all of these can also be set from the helm command line using `--set`.
@@ -20,7 +20,7 @@ allowedIpRanges:
### Forward zones
You can set as many forward zones as needed by specifying the zone name and forward hosts. Forward hosts can be set by hostname or ip.
You can set as many forward zones as needed by specifying the zone name and forward hosts. Forward hosts can be set by hostname or IP.
```yaml
forwardZones:
@@ -92,7 +92,7 @@ Liveness and readiness probes are implemented by a side-car [healthz container](
## Configuring as an upstream resolver for kube-dns
To configure unbound to act as an upstream resolver for kube-dns edit the `kube-dns` configmap in the kube-system namespace to add the `stubDomains` value as shown below. The forwarding address for the domain should be set to the cluster IP of the unbound service.
To configure unbound to act as an upstream resolver for kube-dns edit the `kube-dns` configmap in the kube-system namespace to add the `stubDomains` value as shown below. The forwarding address for the domain should be set to the ClusterIP of the unbound service.
```yaml
apiVersion: v1