Fix helm docs bug

If the ServiceAccount isn't applied first, we get an error since the Pod
references a non-existing ServiceAccount
pull/6854/head
Luke Kysow 2019-11-29 09:17:56 -08:00
parent fd3c56ff68
commit 7b9f63af15
No known key found for this signature in database
GPG Key ID: FA168D4DC3F04307
1 changed files with 10 additions and 10 deletions

View File

@ -47,6 +47,11 @@ HTTP request with the static text "hello world".
```yaml
apiVersion: v1
kind: ServiceAccount
metadata:
name: static-server
---
apiVersion: v1
kind: Pod
metadata:
name: static-server
@ -65,11 +70,6 @@ spec:
name: http
# If ACLs are enabled, the serviceAccountName must match the Consul service name.
serviceAccountName: static-server
---
apiVersion: v1
kind: ServiceAccount
metadata:
name: static-server
```
The only change for Connect is the addition of the
@ -104,6 +104,11 @@ connection via Connect.
```yaml
apiVersion: v1
kind: ServiceAccount
metadata:
name: static-client
---
apiVersion: v1
kind: Pod
metadata:
name: static-client
@ -120,11 +125,6 @@ spec:
args: [ "while true; do sleep 30; done;" ]
# If ACLs are enabled, the serviceAccountName must match the Consul service name.
serviceAccountName: static-client
---
apiVersion: v1
kind: ServiceAccount
metadata:
name: static-client
```
Pods must specify upstream dependencies with the