brand changes have been done
This commit is contained in:
govardhan
@ -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 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.
|
||||
In essence, you create object store under connectVM, either using Horizon or Swift module of **connectVM** 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.
|
||||
|
||||
@ -26,15 +26,15 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline")
|
||||
|
||||
No. 1 **Hosting**
|
||||
|
||||
You need a 3Engines Cloud hosting account with Horizon interface <https://3engine.rootxwire.com/>.
|
||||
You need a connectVM Cloud hosting account with Horizon interface <https://console.connectvm.com/>.
|
||||
|
||||
The resources that you require and use will reflect on the state of your account wallet. Check your account statistics at <https://portal.3Engines.com/>.
|
||||
The resources that you require and use will reflect on the state of your account wallet. Check your account statistics at <https://portal.connectVM.com/>.
|
||||
|
||||
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 3Engines Magnum](How-To-Access-Kubernetes-Cluster-Post-Deployment-Using-Kubectl-On-3Engines-Cloud-3Engines-Magnum.html.md)
|
||||
[How To Access Kubernetes Cluster Post Deployment Using Kubectl On connectVM Cloud connectVM Magnum](How-To-Access-Kubernetes-Cluster-Post-Deployment-Using-Kubectl-On-connectVM-Cloud-connectVM-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:
|
||||
|
||||
@ -54,24 +54,24 @@ No. 3 **Handling Helm**
|
||||
|
||||
To install Velero, we shall use Helm:
|
||||
|
||||
[Deploying Helm Charts on Magnum Kubernetes Clusters on 3Engines Cloud Cloud](Deploying-Helm-Charts-on-Magnum-Kubernetes-Clusters-on-3Engines-Cloud-Cloud.html.md).
|
||||
[Deploying Helm Charts on Magnum Kubernetes Clusters on connectVM Cloud Cloud](Deploying-Helm-Charts-on-Magnum-Kubernetes-Clusters-on-connectVM-Cloud-Cloud.html.md).
|
||||
|
||||
No. 4 **An object storage S3 bucket available**
|
||||
|
||||
To create one, you can access object storage with Horizon interface or CLI.
|
||||
|
||||
Horizon commands
|
||||
: [How to use Object Storage on 3Engines Cloud](../s3/How-to-use-Object-Storage-on-3Engines-Cloud.html.md).
|
||||
: [How to use Object Storage on connectVM Cloud](../s3/How-to-use-Object-Storage-on-connectVM-Cloud.html.md).
|
||||
|
||||
CLI
|
||||
: You can also use command such as
|
||||
|
||||
```
|
||||
3Engines container
|
||||
connectVM container
|
||||
|
||||
```
|
||||
|
||||
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)
|
||||
to work with object storage. For more information see [How to access object storage using connectVM CLI on connectVM Cloud](../connectVMcli/How-to-access-object-storage-using-connectVM-CLI-on-connectVM-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 3Engines. They are necessary to access private bucket (container). Generate them on your own by executing the following commands:
|
||||
First fetch EC2 credentials from connectVM. They are necessary to access private bucket (container). Generate them on your own by executing the following commands:
|
||||
|
||||
```
|
||||
3Engines ec2 credentials create
|
||||
3Engines ec2 credentials list
|
||||
connectVM ec2 credentials create
|
||||
connectVM ec2 credentials list
|
||||
|
||||
```
|
||||
|
||||
@ -134,12 +134,12 @@ 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 3Engines
|
||||
> bucket: ## enter name of bucket created in connectVM
|
||||
> default: true
|
||||
> config:
|
||||
> region: default
|
||||
> s3ForcePathStyle: true
|
||||
> s3Url: ## enter URL of object storage (for example "https://s3.waw4-1.3Engines.com")
|
||||
> s3Url: ## enter URL of object storage (for example "https://s3.waw4-1.connectVM.com")
|
||||
> credentials:
|
||||
> secretContents: ## enter access and secret key to ec2 bucket. This configuration will create kubernetes secret.
|
||||
> cloud: |
|
||||
@ -176,12 +176,12 @@ configuration:
|
||||
backupStorageLocation:
|
||||
provider: aws
|
||||
name: ## enter name of backup storage location (could be anything)
|
||||
bucket: ## enter name of bucket created in 3Engines
|
||||
bucket: ## enter name of bucket created in connectVM
|
||||
default: true
|
||||
config:
|
||||
region: waw3-1
|
||||
s3ForcePathStyle: true
|
||||
s3Url: ## enter URL of object storage (for example "https://s3.waw3-1.3Engines.com")
|
||||
s3Url: ## enter URL of object storage (for example "https://s3.waw3-1.connectVM.com")
|
||||
credentials:
|
||||
secretContents: ## enter access and secret key to ec2 bucket. This configuration will create kubernetes secret.
|
||||
cloud: |
|
||||
@ -218,12 +218,12 @@ configuration:
|
||||
backupStorageLocation:
|
||||
provider: aws
|
||||
name: ## enter name of backup storage location (could be anything)
|
||||
bucket: ## enter name of bucket created in 3Engines
|
||||
bucket: ## enter name of bucket created in connectVM
|
||||
default: true
|
||||
config:
|
||||
region: default
|
||||
s3ForcePathStyle: true
|
||||
s3Url: ## enter URL of object storage (for example "https://s3.waw3-2.3Engines.com")
|
||||
s3Url: ## enter URL of object storage (for example "https://s3.waw3-2.connectVM.com")
|
||||
credentials:
|
||||
secretContents: ## enter access and secret key to ec2 bucket. This configuration will create kubernetes secret.
|
||||
cloud: |
|
||||
@ -260,12 +260,12 @@ configuration:
|
||||
backupStorageLocation:
|
||||
provider: aws
|
||||
name: ## enter name of backup storage location (could be anything)
|
||||
bucket: ## enter name of bucket created in 3Engines
|
||||
bucket: ## enter name of bucket created in connectVM
|
||||
default: true
|
||||
config:
|
||||
region: default
|
||||
s3ForcePathStyle: true
|
||||
s3Url: ## enter URL of object storage (for example "https://s3.fra1-2.3Engines.com")
|
||||
s3Url: ## enter URL of object storage (for example "https://s3.fra1-2.connectVM.com")
|
||||
credentials:
|
||||
secretContents: ## enter access and secret key to ec2 bucket. This configuration will create kubernetes secret.
|
||||
cloud: |
|
||||
@ -313,7 +313,7 @@ configuration:
|
||||
config:
|
||||
region: default
|
||||
s3ForcePathStyle: true
|
||||
s3Url: https://s3.waw4-1.3Engines.com
|
||||
s3Url: https://s3.waw4-1.connectVM.com
|
||||
credentials:
|
||||
secretContents: ## enter access and secret key to ec2 bucket. This configuration will create kubernetes secret.
|
||||
cloud: |
|
||||
@ -355,7 +355,7 @@ configuration:
|
||||
config:
|
||||
region: waw3-1
|
||||
s3ForcePathStyle: true
|
||||
s3Url: https://s3.waw3-1.3Engines.com
|
||||
s3Url: https://s3.waw3-1.connectVM.com
|
||||
credentials:
|
||||
secretContents: ## enter access and secret key to ec2 bucket. This configuration will create kubernetes secret.
|
||||
cloud: |
|
||||
@ -397,7 +397,7 @@ configuration:
|
||||
config:
|
||||
region: default
|
||||
s3ForcePathStyle: true
|
||||
s3Url: https://s3.waw3-2.3Engines.com
|
||||
s3Url: https://s3.waw3-2.connectVM.com
|
||||
credentials:
|
||||
secretContents: ## enter access and secret key to ec2 bucket. This configuration will create kubernetes secret.
|
||||
cloud: |
|
||||
@ -439,7 +439,7 @@ configuration:
|
||||
config:
|
||||
region: default
|
||||
s3ForcePathStyle: true
|
||||
s3Url: https://s3.fra1-2.3Engines.com
|
||||
s3Url: https://s3.fra1-2.connectVM.com
|
||||
credentials:
|
||||
secretContents: ## enter access and secret key to ec2 bucket. This configuration will create kubernetes secret.
|
||||
cloud: |
|
||||
|
||||
Reference in New Issue
Block a user