Skip to content

Commit 52aaa25

Browse files
rasika-chivaterasika-chivate
authored
Merge pull request #201 from percona/open_external_links_new_tabs
open_external_links_new_tabs
2 parents 2d935e8 + 3627fd9 commit 52aaa25

6 files changed

+20
-20
lines changed

‎docs/contribute.md

+5-5
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22

33
Thank you for deciding to contribute and help us improve Percona Everest! We also contribute to other open source projects and communities! Let’s make technology better!
44

5-
By contributing, you agree to the [Percona Community code of conduct](https://percona.community/contribute/coc/).
5+
By contributing, you agree to the [Percona Community code of conduct](https://percona.community/contribute/coc/){:target="_blank"}.
66

77
We welcome all kinds of contributions so here's how you can get involved:
88

@@ -13,13 +13,13 @@ We welcome all kinds of contributions so here's how you can get involved:
1313

1414
## Submit a bug report or feature request
1515

16-
If you find a bug in Percona Everest, you can submit a report via the [Percona Everest Community Forum](https://forums.percona.com).
16+
If you find a bug in Percona Everest, you can submit a report via the [Percona Everest Community Forum](https://forums.percona.com){:target="_blank"}.
1717
Start by searching the open topics for a similar report. If you find that someone else has already reported the same issue, you can upvote that report to increase its visibility.
1818

1919
If there is no existing report, submit a report following these steps:
2020
{.power-number}
2121

22-
1. Sign in to [Percona Everest Forum](https://forums.percona.com). You will need to create an account if you do not have one.
22+
1. Sign in to [Percona Everest Forum](https://forums.percona.com){:target="_blank"}. You will need to create an account if you do not have one.
2323

2424
2. Create a report that:
2525
* describes the steps to reproduce the issue
@@ -46,8 +46,8 @@ Found a typo or didn't find what you needed? Here's how you can contribute to th
4646

4747
To contribute to the documentation, you should be familiar with the following technologies:
4848

49-
* [Markdown](https://www.markdownguide.org/getting-started/) markup language. We write the documentation in it.
50-
* [git](https://git-scm.com/) and [GitHub](https://guides.github.com/activities/hello-world/)
49+
* [Markdown](https://www.markdownguide.org/getting-started/){:target="_blank"} markup language. We write the documentation in it.
50+
* [git](https://git-scm.com/){:target="_blank"} and [GitHub](https://guides.github.com/activities/hello-world/){:target="_blank"}
5151

5252
The `.md` files are in the `docs/` directory.
5353

‎docs/install/installEverestCLI.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@
33
!!! info "Important"
44
Installing the Percona Everest CLI is only necessary if you want to use it to install Percona Everest; it is **not** required if you prefer to install Percona Everest with Helm.
55

6-
You can download the latest version of Everest CLI by visiting the latest release page in [this repository](https://github.com/percona/everest/releases/latest).
6+
You can download the latest version of Everest CLI by visiting the latest release page in [this repository](https://github.com/percona/everest/releases/latest){:target="_blank"}.
77

88

99
=== "Linux and WSL"

‎docs/install/install_everest_helm_charts.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -5,9 +5,9 @@
55

66
For more details, refer to the [Container Registry Deprecation documentation](https://cloud.google.com/artifact-registry/docs/transition/prepare-gcr-shutdown){:target="_blank"}.
77

8-
This section explains how to install Percona Everest using [Helm](https://helm.sh/) as an alternative to `everestctl`. Helm charts simplify the deployment process by packaging all necessary resources and configurations, making them ideal for automating and managing installations in Kubernetes environments.
8+
This section explains how to install Percona Everest using [Helm](https://helm.sh/){:target="_blank"} as an alternative to `everestctl`. Helm charts simplify the deployment process by packaging all necessary resources and configurations, making them ideal for automating and managing installations in Kubernetes environments.
99

10-
Percona Helm charts can be found in [percona/percona-helm-charts]( https://github.com/percona/percona-helm-charts/tree/main/charts/everest) repository in Github.
10+
Percona Helm charts can be found in [percona/percona-helm-charts]( https://github.com/percona/percona-helm-charts/tree/main/charts/everest){:target="_blank"} repository in Github.
1111

1212
## Install Percona Everest and deploy database namespaces
1313

‎docs/reference/migration_guide.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -104,9 +104,9 @@ To migrate from PMM DBaaS to Percona Everest:
104104
!!! note alert alert-primary "Note"
105105
- The restoration won't be available for you in the web UI, you'll need to refer to the corresponding operator's documentation for instructions on how to do this.
106106

107-
- For PXC https://docs.percona.com/percona-operator-for-mysql/pxc/backups-restore.html
108-
- For PSMDB https://docs.percona.com/percona-operator-for-mongodb/backups-restore.html
109-
- For PostgreSQL https://docs.percona.com/percona-operator-for-postgresql/2.0/backups-restore.html
107+
- For [PXC](https://docs.percona.com/percona-operator-for-mysql/pxc/backups-restore.html){:target="_blank"}
108+
- For [PSMDB](https://docs.percona.com/percona-operator-for-mongodb/backups-restore.html){:target="_blank"}
109+
- For [PostgreSQL](https://docs.percona.com/percona-operator-for-postgresql/2.0/backups-restore.html){:target="_blank"}
110110

111111
- Each time you run a database cluster, repeat this step.
112112

‎docs/uninstall/uninstallEverest.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ To uninstall Percona Everest, follow these steps:
1919
everestctl uninstall
2020
```
2121

22-
2. Remove the unused [Custom Resource Definitions (CRDs)](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/).
22+
2. Remove the unused [Custom Resource Definitions (CRDs)](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/){:target="_blank"}.
2323

2424
!!! caution alert alert-warning "warning"
2525

@@ -35,9 +35,9 @@ During the installation of Everest, the following operators are installed:
3535

3636
Besides the operators mentioned above, you must have installed at least one of the following operators.
3737

38-
- [Percona Operator for MySQL(PXC)](https://docs.percona.com/percona-operator-for-mysql/pxc/index.html)
39-
- [Percona Operator for MongoDB(PSMDB)](https://docs.percona.com/percona-operator-for-mongodb/index.html)
40-
- [Percona Operator for PostgreSQL](https://docs.percona.com/percona-operator-for-postgresql/2.0/index.html)
38+
- [Percona Operator for MySQL(PXC)](https://docs.percona.com/percona-operator-for-mysql/pxc/index.html){:target="_blank"}
39+
- [Percona Operator for MongoDB(PSMDB)](https://docs.percona.com/percona-operator-for-mongodb/index.html){:target="_blank"}
40+
- [Percona Operator for PostgreSQL](https://docs.percona.com/percona-operator-for-postgresql/2.0/index.html){:target="_blank"}
4141

4242

4343
### List of CRDs for the operators

‎docs/upgrade/upgrade_operators.md

+5-5
Original file line numberDiff line numberDiff line change
@@ -24,28 +24,28 @@ To upgrade database operators via the Percona Everest UI:
2424

2525
3. Once the upgrade for the database operators becomes available, you can initiate the upgrade process by clicking on **Upgrade**.
2626

27-
![!image](images/upgrade_buttons_page.png)
27+
![!image](../images/upgrade_buttons_page.png)
2828

2929

3030
4. A page is displayed showcasing the upgrades available for the various operators.
3131

3232

33-
![!image](images/show_operators_upgrades.png)
33+
![!image](../images/show_operators_upgrades.png)
3434

3535

3636
5. Click **Upgrade Operators**. A confirmation pop-up will appear, asking if you want to proceed with the upgrade.
3737

3838
39-
![!image](images/upgrade_operators_confirmation.png)
39+
![!image](../images/upgrade_operators_confirmation.png)
4040

4141
4242
6. After clicking on **Upgrade**, you will see a page displaying pending actions. The pending actions indicate that you need to restart the database to utilize the updated CR version.
4343

44-
![!image](images/operators_upgrade_dependency.png)
44+
![!image](../images/operators_upgrade_dependency.png)
4545

4646
7. Click on the pending **Actions**. A confirmation pop-up will appear, asking if you want to **Upgrade CRD version**:
4747

48-
![!image](images/CRD_upgrade_confirmation_1.png)
48+
![!image](../images/CRD_upgrade_confirmation_1.png)
4949

5050
8. Click on **Upgrade** to upgrade the operators.
5151

0 commit comments

Comments
 (0)