admin/3engines_doc
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

brand changed

Browse Source
This commit is contained in:
govardhan
2025-07-04 09:34:25 +05:30
parent 1ee37aea8b
commit faadd4e38d
129 changed files with 1069 additions and 1068 deletions
Download Patch File Download Diff File Expand all files Collapse all files

22
docs/kubernetes/Backup-of-Kubernetes-Cluster-using-Velero.html.md
View File

@ -6,7 +6,7 @@ What is Velero[🔗](#what-is-velero "Permalink to this headline")
[Velero](https://velero.io) is the official open source project from VMware. It can back up all Kubernetes API objects and persistent volumes from the cluster on which it is installed. Backed up objects can be restored on the same cluster, or on a new one. Using a package like Velero is essential for any serious development in the Kubernetes cluster.
In essence, you create object store under OpenStack, either using Horizon or Swift module of **openstack** command and then save cluster state into it. Restoring is the same in reverse – read from that object store and save it to a Kubernetes cluster.
In essence, you create object store under 3Engines, either using Horizon or Swift module of **3Engines** command and then save cluster state into it. Restoring is the same in reverse – read from that object store and save it to a Kubernetes cluster.
Velero has its own CLI command system so it is possible to automate creation of backups using cron jobs.
@ -34,7 +34,7 @@ No. 2 **How to Access Kubernetes cluster post-deployment**
We shall also assume that you have one or more Kubernetes clusters ready and accessible via a **kubectl** command:
[How To Access Kubernetes Cluster Post Deployment Using Kubectl On 3Engines Cloud OpenStack Magnum](How-To-Access-Kubernetes-Cluster-Post-Deployment-Using-Kubectl-On-3Engines-Cloud-OpenStack-Magnum.html.md)
[How To Access Kubernetes Cluster Post Deployment Using Kubectl On 3Engines Cloud 3Engines Magnum](How-To-Access-Kubernetes-Cluster-Post-Deployment-Using-Kubectl-On-3Engines-Cloud-3Engines-Magnum.html.md)
The result of that article will be setting up of system variable **KUBECONFIG**, which points to the configuration file for access to the Kubernetes cloud. A typical command will be:
@ -67,11 +67,11 @@ CLI
: You can also use command such as
```
openstack container
3Engines container
```
to work with object storage. For more information see [How to access object storage using OpenStack CLI on 3Engines Cloud](../openstackcli/How-to-access-object-storage-using-OpenStack-CLI-on-3Engines-Cloud.html.md)
to work with object storage. For more information see [How to access object storage using 3Engines CLI on 3Engines Cloud](../3Enginescli/How-to-access-object-storage-using-3Engines-CLI-on-3Engines-Cloud.html.md)
Either way, we shall assume that there is a container called “bucketnew”:
@ -95,11 +95,11 @@ It will be necessary to have access to a Kubernetes cluster, v1.16 or later, wit
### Installation step 1 Getting EC2 client credentials[🔗](#installation-step-1-getting-ec2-client-credentials "Permalink to this headline")
First fetch EC2 credentials from OpenStack. They are necessary to access private bucket (container). Generate them on your own by executing the following commands:
First fetch EC2 credentials from 3Engines. They are necessary to access private bucket (container). Generate them on your own by executing the following commands:
```
openstack ec2 credentials create
openstack ec2 credentials list
3Engines ec2 credentials create
3Engines ec2 credentials list
```
@ -134,7 +134,7 @@ WAW4-1WAW3-1WAW3-2FRA1-2
> backupStorageLocation:
> provider: aws
> name: ## enter name of backup storage location (could be anything)
> bucket: ## enter name of bucket created in openstack
> bucket: ## enter name of bucket created in 3Engines
> default: true
> config:
> region: default
@ -176,7 +176,7 @@ configuration:
backupStorageLocation:
provider: aws
name: ## enter name of backup storage location (could be anything)
bucket: ## enter name of bucket created in openstack
bucket: ## enter name of bucket created in 3Engines
default: true
config:
region: waw3-1
@ -218,7 +218,7 @@ configuration:
backupStorageLocation:
provider: aws
name: ## enter name of backup storage location (could be anything)
bucket: ## enter name of bucket created in openstack
bucket: ## enter name of bucket created in 3Engines
default: true
config:
region: default
@ -260,7 +260,7 @@ configuration:
backupStorageLocation:
provider: aws
name: ## enter name of backup storage location (could be anything)
bucket: ## enter name of bucket created in openstack
bucket: ## enter name of bucket created in 3Engines
default: true
config:
region: default