Skip to content

Fix minor doc inconsistencies around mariadb invokation #3019

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/examples/stateful-applications.md
Original file line number Diff line number Diff line change
Expand Up @@ -109,7 +109,7 @@ kubectl run db-mariadb-galera-client --rm --tty -i \
--restart='Never' --namespace default \
--image docker.io/bitnami/mariadb-galera:11.4.5-debian-12-r6 \
--command \
-- mysql -h db-mariadb-galera.liqo-demo -uuser -ppassword my_database
-- mariadb -h db-mariadb-galera.liqo-demo -uuser -p'password' my_database
```

And then create an example table and insert some data:
Expand Down Expand Up @@ -159,9 +159,9 @@ And querying again for your data:
```bash
kubectl run db-mariadb-galera-client --rm --tty -i \
--restart='Never' --namespace default \
--image docker.io/bitnami/mariadb-galera:10.6.7-debian-10-r56 \
--image docker.io/bitnami/mariadb-galera:11.4.5-debian-12-r6 \
--command \
-- mysql -h db-mariadb-galera.liqo-demo -uuser -ppassword my_database \
-- mariadb -h db-mariadb-galera.liqo-demo -uuser -p'password' my_database \
--execute "SELECT * FROM People;"
```

Expand Down
4 changes: 2 additions & 2 deletions docs/features/peering.md
Original file line number Diff line number Diff line change
Expand Up @@ -38,9 +38,9 @@ The approach is schematized at a high level in the figure below.

```{warning}
The standard *liqoctl* peer command requires the machine running it to have simultaneous access to both cluster API servers, through their *kubeconfigs*.
If this is not possible, refer to the advanced guide to learn how to perform the [peering manually](/advanced/manual-peering) without having contemporary access to both clusters.
If this is not possible, refer to the advanced guide to learn how to perform the [peering manually](/advanced/manual-peering) without having simultaneous access to both clusters.
```

```{admonition} Note
The user can adopt different peering approaches depending if it has contemporary access to both clusters or not, as described in the [dedicated page](/advanced/peering-strategies.md).
The user can adopt different peering approaches depending if it has simultaneous access to both clusters or not, as described in the [dedicated page](/advanced/peering-strategies.md).
```