Skip to content
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

Update the backup Kyma docu #18760

Merged
merged 7 commits into from
Nov 20, 2024
Merged

Update the backup Kyma docu #18760

merged 7 commits into from
Nov 20, 2024

Conversation

mmitoraj
Copy link
Contributor

Description

Changes proposed in this pull request:

  • Updated the backup Kyma documentation
  • Deleted the steps for creating a periodic snapshot job

Related issue(s)

@mmitoraj mmitoraj requested a review from a-thaler October 30, 2024 15:37
@mmitoraj mmitoraj requested a review from a team as a code owner October 30, 2024 15:37
Copy link

netlify bot commented Oct 30, 2024

👷 Deploy request for kyma-project pending review.

Visit the deploys page to approve it

Name Link
🔨 Latest commit cb99c4f

@kyma-bot kyma-bot added cla: yes Indicates the PR's author has signed the CLA. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Oct 30, 2024
Copy link

netlify bot commented Oct 30, 2024

Deploy Preview for kyma-project-docs-preview ready!

Name Link
🔨 Latest commit cb99c4f
🔍 Latest deploy log https://app.netlify.com/sites/kyma-project-docs-preview/deploys/673df127f6a37800086b239b
😎 Deploy Preview https://deploy-preview-18760--kyma-project-docs-preview.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@mmitoraj
Copy link
Contributor Author

@a-thaler Hi Icke, I still have some doubts:

  1. Does the operation described in the Gardener tab look the same as we describe it on Help Portal (that's what I added in the PR)?
  2. Are the AKS and GKE tabs still valid?


### Steps
#### **AKS**
Copy link
Contributor

@a-thaler a-thaler Oct 30, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As we now just use the default class and nothing specific is needed anymore, we can remove the hyperscaler specific steps, just keep the Gardener instructions without mentioning Gardener

## Back Up Resources Using Third-Party Tools
>[!WARNING]
> Third-party tools like Velero are not currently supported. These tools may have limitations and might not fully support automated cluster backups. They often require specific access rights to cluster infrastructure, which may not be available in Kyma's managed offerings, where access rights to the infrastructure account are restricted.
Taking volume snapshots is possible thanks to [Container Storage Interface (CSI) drivers](https://kubernetes-csi.github.io/docs/), which allow third-party storage providers to expose storage systems in Kubernetes. The driver must be specified in the VolumeSnapshotClass resource.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would mention that there is a default VolumeSnapshotClass available usually so that configring the driver is not your concern

a-thaler
a-thaler previously approved these changes Nov 20, 2024
@kyma-bot kyma-bot added the lgtm Looks good to me! label Nov 20, 2024
## Back Up Resources Using Third-Party Tools
>[!WARNING]
> Third-party tools like Velero are not currently supported. These tools may have limitations and might not fully support automated cluster backups. They often require specific access rights to cluster infrastructure, which may not be available in Kyma's managed offerings, where access rights to the infrastructure account are restricted.
Taking volume snapshots is possible thanks to [Container Storage Interface (CSI) drivers](https://kubernetes-csi.github.io/docs/), which allow third-party storage providers to expose storage systems in Kubernetes. The driver must be specified in the VolumeSnapshotClass resource. Kyma clusters usually have a default VolumeSnapshotClass available. If you use the default resource, you don't have to confgure the driver.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Taking volume snapshots is possible thanks to [Container Storage Interface (CSI) drivers](https://kubernetes-csi.github.io/docs/), which allow third-party storage providers to expose storage systems in Kubernetes. The driver must be specified in the VolumeSnapshotClass resource. Kyma clusters usually have a default VolumeSnapshotClass available. If you use the default resource, you don't have to confgure the driver.
Taking volume snapshots is possible thanks to [Container Storage Interface (CSI) drivers](https://kubernetes-csi.github.io/docs/), which allow third-party storage providers to expose storage systems in Kubernetes. The driver must be specified in the VolumeSnapshotClass resource. Kyma clusters usually have a default VolumeSnapshotClass available. If you use the default resource, you don't have to configure the driver.

@kyma-bot kyma-bot removed the lgtm Looks good to me! label Nov 20, 2024
@kyma-bot kyma-bot added the lgtm Looks good to me! label Nov 20, 2024
@kyma-bot kyma-bot merged commit 5df30ed into kyma-project:main Nov 20, 2024
7 of 8 checks passed
@mmitoraj mmitoraj deleted the backup branch November 20, 2024 14:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla: yes Indicates the PR's author has signed the CLA. lgtm Looks good to me! size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants