I noticed a typo in a recent blog post, and a similar typo appears in
the comments for some examples. This PR corrects these typos.
Signed-off-by: Bridget Kromhout <bridget@kromhout.org>
* docs(configure-redis-using-configmap): update for clarity
Signed-off-by: Jai Govindani <jai@honestbank.com>
* fix(configure-redis-using-configmap): incorrect volumeMount index
Signed-off-by: Jai Govindani <jai@honestbank.com>
* fix(configure-redis-using-configmap): show Pod status as Running, separate commands from output
Signed-off-by: Jai Govindani <jai@honestbank.com>
* fix(configure-redis-using-configmap): typo
Signed-off-by: Jai Govindani <jai@honestbank.com>
* fix(configure-redis-using-configmap): configmap name
Signed-off-by: Jai Govindani <jai@honestbank.com>
The stateless application tutorial is littered with unsuitable terminology. This update switches the database technology to a database that has already updated their own terminology as well as removes the terminology from the tutorial itself.
The advanced logging tutorial followup is set to Draft as it will take a larger effort to convert that, and I'm not convinced its even in a working state right now.
A followup PR to the examples repo to be referenced here will be made.
Addresses #22918
Signed-off-by: Paul Czarkowski <username.taken@gmail.com>
address comments in PR
Signed-off-by: Paul Czarkowski <username.taken@gmail.com>
remove confusing comment about dns, we can assume k8s has kube-dns
Signed-off-by: Paul Czarkowski <username.taken@gmail.com>
This PR updates the go.mod file so that tests of the example manifests
are run against the 1.20 branch. The missing test cases for newly added
examples are also added. To perform tests on your local machine, run the
following command on the root of your local clone:
```
go test k8s.io/website/content/en/examples
```
* Enhancements in clarity to docs/tasks/access-application-cluster/connecting-frontend-backend.md
* Code review comments
* Reverting name of service due to backed value in Dockerimage
The commit (a79db9d5de) made the sample
YAML for Ingress a standalone file, but it was placed into a NEW
`examples/ingress` directory. This PR moves it to
`examples/service/networking` subdirectory where all other Ingress
examples are located. Having a single file under a dedicated directory
seems not good.
Clarify that `REMOTE_PORT` is interpreted as identifying a _Service_ port when provided `TYPE` is `service`.
Also, highlight support for specifying a named port as `REMOTE_PORT`.