mirror of
https://github.com/kubernetes-sigs/external-dns.git
synced 2025-09-20 15:41:01 +02:00
Use consistent headless service name
Fix a typo and update the headless service name to be consistent.
This commit is contained in:
parent
4c7c3be807
commit
defe8b7ffc
@ -17,7 +17,7 @@ A simple deploy could look like this:
|
||||
apiVersion: apps/v1
|
||||
kind: Deployment
|
||||
metadata:
|
||||
name: exeternal-dns
|
||||
name: external-dns
|
||||
spec:
|
||||
strategy:
|
||||
type: Recreate
|
||||
@ -111,7 +111,7 @@ spec:
|
||||
|
||||
### Kafka Stateful Set
|
||||
|
||||
First lets deploy a Kafka Stateful set, a simple example(a lot of stuff is missing) with a headless service called `kafka-hsvc`
|
||||
First lets deploy a Kafka Stateful set, a simple example(a lot of stuff is missing) with a headless service called `ksvc`
|
||||
|
||||
```yaml
|
||||
apiVersion: apps/v1beta1
|
||||
@ -155,7 +155,7 @@ spec:
|
||||
requests:
|
||||
storage: 500Gi
|
||||
```
|
||||
Very important here, is to set the `hostport`(only works if the PodSecurityPolicy allows it)! and in case your app requires an actual hostname inside the container, unlike Kafka, which can advertise on another address, you have to set the hostname yourself.
|
||||
Very important here, is to set the `hostPort`(only works if the PodSecurityPolicy allows it)! and in case your app requires an actual hostname inside the container, unlike Kafka, which can advertise on another address, you have to set the hostname yourself.
|
||||
|
||||
### Headless Service
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user