Skip to content

Commit

Permalink
Merge branch '1.4.0' into Helm_charts
Browse files Browse the repository at this point in the history
  • Loading branch information
rasika-chivate committed Jan 7, 2025
2 parents d3a46c4 + f093e53 commit 2fbb126
Show file tree
Hide file tree
Showing 4 changed files with 36 additions and 7 deletions.
1 change: 1 addition & 0 deletions docs/administer/rbac.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,6 @@
# Role-based access control (RBAC)


!!! warning "Disclaimer"
RBAC is currently in **Technical Preview**. Early adopters are advised to use this feature only for testing purposes and not in production environments.

Expand Down
1 change: 1 addition & 0 deletions docs/css/design.css
Original file line number Diff line number Diff line change
Expand Up @@ -262,6 +262,7 @@
vertical-align: baseline;
padding: 0 0.2em 0.1em;
border-radius: 0.15em;
white-space: pre-wrap; /* Ensure long lines wrap */
}
.md-typeset .highlight code span,
.md-typeset code,
Expand Down
14 changes: 12 additions & 2 deletions docs/reference/known_limitations.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,15 +23,25 @@ We are developing a new feature that will allow you to modify these settings dir
On the Percona Everest UI, navigate to the **Restores** tab, locate the latest restore object, click `...`, and delete it. Then, attempt to restore it again.


## MongoDB
## Databases

- MongoDB 4.4 will no longer be supported, preventing users from upgrading the PSMDB operator if any database is running version 4.4.

- Do not create a full backup on an empty database. Instead, perform a full backup after adding some data to the database.
- Do not perform a full backup of an empty MongoDB database. Instead, ensure that you add some data to the database before creating a full backup.

- If you attempt to delete a MongoDB cluster stuck in the **initializing** state due to insufficient resources, the cluster will remain in the deleting state indefinitely. This issue is caused by a [bug](https://perconadev.atlassian.net/browse/K8SPSMDB-1208){:target="_blank"} in the PSMDB operator.


- If you attempt to delete a MongoDB and MySQL cluster stuck in the **initializing** state due to insufficient resources, the cluster will remain in the deleting state indefinitely. This issue is caused by a [bug](https://perconadev.atlassian.net/browse/K8SPSMDB-1208){:target="_blank"} in the PSMDB operator.

**Workaround**

1. Run the command:

`kubectl edit psmdb/<DBName> -n <Namespace>`

2. Delete the finalizer called `delete-pods-in-order`.

## Upgrading operators

- When you upgrade PostgreSQL operators to version 2.4.1, the database transitions to the **Initializing** state as part of the upgrade process. However, this **Initializing** state does not cause any downtime.
Expand Down
27 changes: 22 additions & 5 deletions docs/use/CreateStorage.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,11 +13,28 @@ Everest supports S3-compatible backup locations, which means you can use [AWS S3
To create a backup storage location:
{.power-number}

1. Go to **Settings > Backup storages** and click **Add Backup storage**.
2. In the **Name** field, specify a location name using only lowercase alphanumeric characters or hyphens.
3. Select the **Namepaces** where the backup storage should be available.
4. Enter your credentials, making sure to use regional AWS STS endpoints instead of the global endpoint: `https://s3.<region>.amazonaws.com`.
Using an endpoint that is geographically closer to your application reduces latency and provides better response times.
1. Go to Backup storage settings:

Navigate to <i class="uil uil-cog"></i> **Settings > Backup storages**, then click **Add Backup storage**.

2. Fill in the Required Fields:

- **Name**: Enter a name using only lowercase letters, numbers, or hyphens.
- **Description**: (Optional) Add a short description for this backup storage.
- **Namespace**: Select where this backup storage will be available.
- **Type**: Choose S3 Compatible.
- **Bucket Name**: Provide the S3 bucket name where backups will be stored.
- **Region**: Specify the bucket's region (e.g., us-east-1).
- **Endpoint**: Enter the S3-compatible URL (e.g., https://s3.us-east-1.amazonaws.com).
- **Access Key**: Input the access key for your S3 account.
- **Secret Key**: Input the corresponding secret key.

3. Additional Options:
- **Verify TLS Certificate**: Enable this to validate secure connections.
- **Force Path-Style URL Access**: Use this if your storage provider uses path-style URLs.

4. Click **Add** to save your configuration.


## Next steps

Expand Down

0 comments on commit 2fbb126

Please sign in to comment.