change wording for redis leader (#1804)

#### What type of PR is this?

<!--
Add one of the following kinds:
/kind bug
/kind cleanup
/kind feature
-->

/kind documentation

#### What this PR does / why we need it:

We should not be using the outdated redis terms, instead redis now uses
leader / replica.

#### Which issue(s) this PR fixes:
<!--
*Automatically closes linked issue when PR is merged.
Usage: `Fixes #<issue number>`, or `Fixes (paste link of issue)`.
-->
N/A

#### Special notes for your reviewer:
N/A

Signed-off-by: Charlie Drage <charlie@charliedrage.com>
This commit is contained in:
Charlie Drage
2024-01-16 09:49:54 -05:00
committed by GitHub
parent bd868aac79
commit 770da91eec
3 changed files with 13 additions and 13 deletions
+4 -4
View File
@@ -48,20 +48,20 @@ $ kompose -f compose.yml -f docker-guestbook.yml convert
INFO Kubernetes file "frontend-service.yaml" created
INFO Kubernetes file "mlbparks-service.yaml" created
INFO Kubernetes file "mongodb-service.yaml" created
INFO Kubernetes file "redis-master-service.yaml" created
INFO Kubernetes file "redis-leader-service.yaml" created
INFO Kubernetes file "redis-replica-service.yaml" created
INFO Kubernetes file "frontend-deployment.yaml" created
INFO Kubernetes file "mlbparks-deployment.yaml" created
INFO Kubernetes file "mongodb-deployment.yaml" created
INFO Kubernetes file "mongodb-claim0-persistentvolumeclaim.yaml" created
INFO Kubernetes file "redis-master-deployment.yaml" created
INFO Kubernetes file "redis-leader-deployment.yaml" created
INFO Kubernetes file "redis-replica-deployment.yaml" created
$ ls
mlbparks-deployment.yaml mongodb-service.yaml redis-replica-service.jsonmlbparks-service.yaml
frontend-deployment.yaml mongodb-claim0-persistentvolumeclaim.yaml redis-master-service.yaml
frontend-deployment.yaml mongodb-claim0-persistentvolumeclaim.yaml redis-leader-service.yaml
frontend-service.yaml mongodb-deployment.yaml redis-replica-deployment.yaml
redis-master-deployment.yaml
redis-leader-deployment.yaml
```
When multiple compose files are provided the configuration is merged. Any configuration that is common will be over ridden by subsequent file.