Coder Social home page Coder Social logo

velero-plugin's Introduction

Overview

GoReportCard Widget

Velero is a utility to back up and restore your Kubernetes resource and persistent volumes.

To do backup/restore on Alibaba Cloud through Velero utility, you need to install and configure velero and velero-plugin for alibabacloud.

Run velero on AlibabaCloud

To set up Velero on AlibabaCloud, you:

  • Download an official release of Velero
  • Create your OSS bucket
  • Create an RAM user for Velero
  • Install the velero and velero-plugin for alibabacloud

Download Velero

  1. Download the latest official release's tarball for your client platform.

    We strongly recommend that you use an official release of Velero. The tarballs for each release contain the velero command-line client. The code in the master branch of the Velero repository is under active development and is not guaranteed to be stable!

  2. Extract the tarball:

    tar -xvf <RELEASE-TARBALL-NAME>.tar.gz -C /dir/to/extract/to 

    We'll refer to the directory you extracted to as the "Velero directory" in subsequent steps.

  3. Move the velero binary from the Velero directory to somewhere in your PATH.

Create OSS bucket

Velero requires an object storage bucket to store backups in, preferrably unique to a single Kubernetes cluster. Create an OSS bucket, replacing placeholders appropriately:

BUCKET=<YOUR_BUCKET>
REGION=<YOUR_REGION>
ossutil mb oss://$BUCKET \
        --storage-class Standard \
        --acl=private

Create RAM user

For more information, see the AlibabaCloud documentation on RAM users guides.

  1. Create the RAM user:

    Follow the AlibabaCloud documentation on RAM users.

    If you'll be using Velero to backup multiple clusters with multiple OSS buckets, it may be desirable to create a unique username per cluster rather than the default velero.

  2. Attach policies to give velero the necessary permissions:

    Note that you'd better release the velero's delete permissions once you have completed your backup or restore task for safety reasons.

    {
        "Version": "1",
        "Statement": [
            {
                "Action": [
                    "ecs:DescribeSnapshots",
                    "ecs:CreateSnapshot",
                    "ecs:DeleteSnapshot",
                    "ecs:DescribeDisks",
                    "ecs:CreateDisk",
                    "ecs:Addtags",
                    "oss:PutObject",
                    "oss:GetObject",
                    "oss:DeleteObject",
                    "oss:GetBucket",
                    "oss:ListObjects",
                    "oss:ListBuckets"
                ],
                "Resource": [
                    "*"
                ],
                "Effect": "Allow"
            }
        ]
    }
  3. Create an access key for the user:

    Follow the AlibabaCloud documentation on create AK.

  4. Create a Velero-specific credentials file (credentials-velero) in your install directory:

    ALIBABA_CLOUD_ACCESS_KEY_ID=<ALIBABA_CLOUD_ACCESS_KEY_ID>
    ALIBABA_CLOUD_ACCESS_KEY_SECRET=<ALIBABA_CLOUD_ACCESS_KEY_SECRET>
    

    where the access key id and secret are the values get from the step 3.

Install velero and velero-plugin for alibabacloud

  1. Set some environment variables

    BUCKET=<YOUR_BUCKET>
    REGION=<YOUR_REGION>
  2. Create and run velero and velero-plugin for alibabacloud

    Run the following command to create and run velero and velero-plugin for alibabacloud

    velero install \
      --provider alibabacloud \
      --image registry.$REGION.aliyuncs.com/acs/velero:1.4.2-2b9dce65-aliyun \
      --bucket $BUCKET \
      --secret-file ./credentials-velero \
      --use-volume-snapshots=false \
      --backup-location-config region=$REGION \
      --use-restic \
      --plugins registry.$REGION.aliyuncs.com/acs/velero-plugin-alibabacloud:v1.0.0-2d33b89 \
      --wait
    

    If you want use an internal oss endpoint, you can add params:

    --backup-location-config region=$REGION,network=internal

    If you want use a oss prefix to store backup files, you can add params:

    --prefix <your oss bucket prefix>

  3. Create ConfigMap for velero restic helper image in your restore cluster

Run the following command to create a velero restic helper configmap in your restore cluster(optional for backup cluster).

kubectl -n velero apply -f install/02-configmap.yaml

  1. Cleanup velero installation

    Run the following command to cleanup the velero installation

    kubectl delete namespace/velero clusterrolebinding/velero
    kubectl delete crds -l component=velero
    

Installing the nginx example (optional)

  1. nginx example without persistent volumes

    Run the following command to create a nginx example without persistent volumes:

    kubectl apply -f examples/base.yaml

    Create a backup:

    velero backup create nginx-backup --include-namespaces nginx-example --wait

    Destroy the nginx example:

    kubectl delete namespaces nginx-example

    Create a restore from nginx-backup:

    velero restore create --from-backup nginx-backup --wait

  2. nginx example with persistent volumes

    Run the following command to create a nginx example with persistent volumes:

    kubectl apply -f examples/with-pv.yaml
    

    Add annotations to pod volume, restic will backup the volume data during backup process.

    kubectl -n nginx-example annotate pod/nginx-deployment-7477779c4f-dxspm backup.velero.io/backup-volumes=nginx-logs
    

    Create a backup:

    velero backup create nginx-backup-volume --include-namespaces nginx-example --wait

    Destroy the nginx example:

    kubectl delete namespaces nginx-example
    

    Create a restore from nginx-backup-volume:

    velero restore create --from-backup nginx-backup-volume --wait

velero-plugin's People

Contributors

haoshuwei avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

velero-plugin's Issues

velero pod errors after updating official velero image to latest version

time="2019-08-30T03:21:45Z" level=info msg="Checking existence of namespace" logSource="pkg/cmd/server/server.go:336" namespace=velero
time="2019-08-30T03:21:45Z" level=info msg="Namespace exists" logSource="pkg/cmd/server/server.go:342" namespace=velero
time="2019-08-30T03:21:47Z" level=info msg="Checking existence of Velero custom resource definitions" logSource="pkg/cmd/server/server.go:371"
time="2019-08-30T03:21:47Z" level=info msg="All Velero custom resource definitions exist" logSource="pkg/cmd/server/server.go:405"
time="2019-08-30T03:21:47Z" level=info msg="Checking that all backup storage locations are valid" logSource="pkg/cmd/server/server.go:412"
An error occurred: some backup storage locations are invalid: error getting backup store for location "default": rpc error: code = Unknown desc = config has invalid keys [prefix]; valid keys are [bucket]

Backup store contains invalid top-level directories: [velero]

What steps did you take and what happened:
[A clear and concise description of what the bug is.]

An error occurred after installed:

time="2022-02-23T13:54:10Z" level=info msg="All Velero custom resource definitions exist" logSource="pkg/cmd/server/server.go:430"
time="2022-02-23T13:54:10Z" level=info msg="Checking that all backup storage locations are valid" logSource="pkg/cmd/server/server.go:437"
An error occurred: some backup storage locations are invalid: backup store for location "default" is invalid: Backup store contains invalid top-level directories: [velero]

What did you expect to happen:

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

Environment:

Install command:

BUCKET=velero-aks
REGION=cn-beijing

velero install
--provider alibabacloud
--image registry.$REGION.aliyuncs.com/acs/velero:1.4.2-2b9dce65-aliyun
--bucket $BUCKET
--secret-file ./credentials-velero
--use-volume-snapshots=false
--backup-location-config region=$REGION
--use-restic
--plugins registry.$REGION.aliyuncs.com/acs/velero-plugin-alibabacloud:v1.0.0-2d33b89
--wait

Velero BackupStorageLocation unavailable

What steps did you take and what happened:
[A clear and concise description of what the bug is.]
velero backupstoragelocation error:

BackupStorageLocation "default" is unavailable: rpc error: code = Unknown
desc = error loading environment from ALIBABA_CLOUD_CREDENTIALS_FILE (/credentials/cloud):
Can''t separate key from value

secret file

[default]
alibaba_cloud_access_key_id = xxx
alibaba_cloud_access_key_secret = xxxx

What did you expect to happen:
The backupstoragelocation status is Available

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

Environment:

  • Velero version: (use ark version): v1.13.0 velero-plugin-alibabacloud:v1.0.0-2d33b89
  • Kubernetes version: (use kubectl version): v1.18.20
  • Kubernetes installer & version:
  • Cloud provider or hardware configuration:
  • OS (e.g. from /etc/os-release):

The bucket you access does not belong to you

What steps did you take and what happened:
[A clear and concise description of what the bug is.]

An error occurred: some backup storage locations are invalid: backup store for location "default" is invalid: rpc error: code = Unknown desc = oss: service returned error: StatusCode=403, ErrorCode=AccessDenied, ErrorMessage="The bucket you access does not belong to you."

What did you expect to happen:

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

Environment:

  • Velero version: (use ark version):
  • Kubernetes version: (use kubectl version):
  • Kubernetes installer & version:
  • Cloud provider or hardware configuration:
  • OS (e.g. from /etc/os-release):

Error attemping to get volume ID for persistent volume

What steps did you take and what happened:

Error occur when trying to backup PV

./velero backup logs prod-2-20190709035918 | grep error
time="2019-07-09T03:59:19Z" level=error msg="Error attempting to get volume ID for persistent volume" backup=velero/prod-2-20190709035918 error="rpc error: code = Unknown desc = spec.FlexVolume.Options['VolumeId'] not found" error.file="/Users/hao/go/src/github.com/AliyunContainerService/velero-plugin/pkg/alibabacloud/volume_snapshotter.go:300" error.function=github.com/AliyunContainerService/velero-plugin/pkg/alibabacloud.getEBSDiskID group=v1 logSource="pkg/backup/item_backupper.go:415" name=d-j6c4ymqw967s58578buo namespace=kube-tools persistentVolume=d-j6c4ymqw967s58578buo resource=pods volumeSnapshotLocation=default
time="2019-07-09T03:59:19Z" level=error msg="Error attempting to get volume ID for persistent volume" backup=velero/prod-2-20190709035918 error="rpc error: code = Unknown desc = unsupported FlexVolume driver: alicloud/nas" error.file="/Users/hao/go/src/github.com/AliyunContainerService/velero-plugin/pkg/alibabacloud/volume_snapshotter.go:277" error.function=github.com/AliyunContainerService/velero-plugin/pkg/alibabacloud.checkFlexVolumeDriver group=v1 logSource="pkg/backup/item_backupper.go:415" name=scmp-d8-nas namespace=product-web persistentVolume=scmp-d8-nas resource=pods volumeSnapshotLocation=default

d-j6c4ymqw967s58578buo is a clouddisk volume
scmp-d8-nas is NAS volume
Both mounted as PV in the same k8s cluster

What did you expect to happen:

Able to backup PV on aliyun CS

Environment:

  • Velero version: (use ark version): v1.0.0
  • Kubernetes version: (use kubectl version):
Client Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.9", GitCommit:"16236ce91790d4c75b79f6ce96841db1c843e7d2", GitTreeState:"clean", BuildDate:"2019-03-25T06:40:24Z", GoVersion:"go1.10.8", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"12+", GitVersion:"v1.12.6-aliyun.1", GitCommit:"8cb561c", GitTreeState:"", BuildDate:"2019-04-22T11:34:20Z", GoVersion:"go1.10.8", Compiler:"gc", Platform:"linux/amd64"}
  • Kubernetes installer & version: aliyun
  • Cloud provider or hardware configuration: aliyun
  • OS (e.g. from /etc/os-release): aliyun linux

PV restore时Disk 创建在错误的zone上

What steps did you take and what happened:
[A clear and concise description of what the bug is.]
velero恢复PV的时候发现阿里云操作日志里有attach disk失败的日志,因为备份的PV和velero阿里云的插件创建出来的disk不在一个zone上,例如我备份的PV在cn-shangh-l, 创建出来的disk却在cn-shanghai-g

What did you expect to happen:
创建的disk和原来备份的PV在同一个zone上

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
在这行代码:https://github.com/AliyunContainerService/velero-plugin/blob/master/velero-plugin-for-alibabacloud/volume_snapshotter.go#L104

func (b *VolumeSnapshotter) CreateVolumeFromSnapshot(snapshotID, volumeType, volumeAZ string, iops *int64) (volumeID string, err error) {
	// describe the snapshot so we can apply its tags to the volume
	snapReq := ecs.CreateDescribeSnapshotsRequest()
	snapReq.SnapshotIds = getJSONArrayString(snapshotID)

	snapRes, err := b.ecs.DescribeSnapshots(snapReq)
	if err != nil {
		return "", errors.WithStack(err)
	}

	if count := len(snapRes.Snapshots.Snapshot); count != 1 {
		return "", errors.Errorf("expected 1 snapshot from DescribeSnapshots for %s, got %v", snapshotID, count)
	}

	tags := getTagsForCluster(snapRes.Snapshots.Snapshot[0].Tags.Tag)

	volumeAZ, err = getMetaData(metadataZoneKey)
	if err != nil {
		return "", errors.Errorf("failed to get zone-id, got %v", err)
	}
.........
}

调用了getMetadata 来读取了velero pod 所在的instance的metadata, 并且用velero pod所在的instance的zone 覆盖了velero传进来的参数:volumeAZ,所以会导致插件创建的disk和velero传的参数不在一个zone上,是否能删除这行代码来修复这个问题?谢谢

Environment:

  • Velero version: (use ark version):
  • Kubernetes version: (use kubectl version):
  • Kubernetes installer & version:
  • Cloud provider or hardware configuration:
  • OS (e.g. from /etc/os-release):

unsupported CSI driver: rook-ceph.rbd.csi.ceph.com

What steps did you take and what happened:
[A clear and concise description of what the bug is.]
backup logs:
level=error msg="Error attempting to get volume ID for persistent volume" backup=velero/production-backup error="rpc error: code = Unknown desc = unsupported CSI driver: rook-ceph.rbd.csi.ceph.com" error.file="/home/regressionTest/go/src/github.com/AliyunContainerService/velero-plugin/velero-plugin-for-alibabacloud/volume_snapshotter.go:264" error.function=main.checkCSIVolumeDriver group=v1 logSource="pkg/backup/item_backupper.go:438" name=pvc-8b09731c-a57f-47d2-98bf-cf98d90ba6bd namespace= persistentVolume=pvc-8b09731c-a57f-47d2-98bf-cf98d90ba6bd resource=persistentvolumes volumeSnapshotLocation=default

What did you expect to happen:
create backup

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

Environment:

  • Velero version: (use ark version):
    Client:
    Version: v1.5.2
    Server:
    Version: v1.2.0
  • Kubernetes version: (use kubectl version):
    Client Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.6",
    Server Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.6",
  • Kubernetes installer & version:
  • Cloud provider or hardware configuration:
  • OS (e.g. from /etc/os-release): Ubuntu 20.04.1 LTS

x509: certificate signed by unknown authority

restore pod logs

[root@YX-Master01 ~]# kubectl -n fluent logs -f fluent-operator-78ff548b4c-rv844
2022-06-15T08:09:28.990Z ERROR controller-runtime.manager Failed to get API Group-Resources {"error": "Get "https://10.255.0.1:443/api?timeout=32s\": x509: certificate signed by unknown authority"}
sigs.k8s.io/controller-runtime/pkg/manager.New
/go/pkg/mod/sigs.k8s.io/[email protected]/pkg/manager/manager.go:312
main.main
/workspace/main.go:100
runtime.main
/usr/local/go/src/runtime/proc.go:255
2022-06-15T08:09:28.991Z ERROR setup unable to start manager {"error": "Get "https://10.255.0.1:443/api?timeout=32s\": x509: certificate signed by unknown authority"}
main.main
/workspace/main.go:102
runtime.main
/usr/local/go/src/runtime/proc.go:255

Environment:

  • Velero version: 1.8.1
  • Kubernetes version: 1.22.3
  • OS : CentOS-7

velero describe

[root@test-1 velero-v1.8.1-linux-amd64]# velero backup describe nats-backup
Name: nats-backup
Namespace: velero
Labels: velero.io/storage-location=default
Annotations: velero.io/source-cluster-k8s-gitversion=v1.22.2
velero.io/source-cluster-k8s-major-version=1
velero.io/source-cluster-k8s-minor-version=22

Phase: Completed

Errors: 0
Warnings: 0

Namespaces:
Included: nats
Excluded:

Resources:
Included: *
Excluded:
Cluster-scoped: auto

Label selector:

Storage Location: default

Velero-Native Snapshot PVs: auto

TTL: 720h0m0s

Hooks:

Backup Format Version: 1.1.0

Started: 2022-06-15 16:03:38 +0800 CST
Completed: 2022-06-15 16:03:47 +0800 CST

Expiration: 2022-07-15 16:03:38 +0800 CST

Total items to be backed up: 22
Items backed up: 22

Velero-Native Snapshots:

velero logs

[root@test-1 velero-v1.8.1-linux-amd64]# velero backup logs nats-backup

velero logs no any messages!

Missing `resticRepoPrefix` config key

What steps did you take and what happened:
Trying to use Restic for NFS-backed volume is not possible because Alicloud Velero plugin does not accept resticRepoPrefix config key. The ResticRepository custom resource fails with restic repository prefix (resticRepoPrefix) not specified in backup storage location's config

What did you expect to happen:
Alicloud Velero plugin should work with Restic.

Anything else you would like to add:
See this issue

Environment:

  • Velero version: (use ark version): v1.6.2
  • Kubernetes version: (use kubectl version): v1.20.4-aliyun.1

When will the new version of velero v1.10.0+ be supported

Describe the solution you'd like
[A clear and concise description of what you want to happen.]
支持 velero v1.10.0 及以上。目前只支持v1.9.0版本

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

Environment:

  • Velero version: (use ark version): v1.10.0
  • Kubernetes version: (use kubectl version): v1.19.3
  • Kubernetes installer & version: v1.22.15

image

  • Cloud provider or hardware configuration:
  • OS (e.g. from /etc/os-release):

Instruction for configuring general velero chart

Hi,

I might be wrong but I've noticed that the helm chart provided with the plugin is basically a specially configured version of the general helm chart of velero that can be used for aws & azure:
https://github.com/helm/charts/tree/master/stable/velero

Maybe we should have instructions for configuring the general chart to work with the velero plugin instead of creating an incompatible fork? We maintain a multi-cloud deployment where we configure and install the same helm charts for several installations and velero is the only chart that is completely different between different providers instead of simply having different values.

Is there any release information or version information for this plugin?

Refer to another issue #33, you have set the plugin version tag as v1.2-991b590. So can we use this version No. as the plugin number?
As we have the scenario on Alicloud cluster to integrate with velero 1.4.0 for k8s landscapes backup/recovery, can this v1.2 velero-plugin be used in this scenario? Any compatible listing of plugin versions and respective Velero versions there for reference?

reading plugin stderr

What steps did you take and what happened:

An error shown during scheduled backup

time="2019-07-24T20:53:18Z" level=info msg="Checking for expired DeleteBackupRequests" controller=backup-deletion logSource="pkg/controller/backup_deletion_controller.go:441"
time="2019-07-24T20:53:18Z" level=info msg="Done checking for expired DeleteBackupRequests" controller=backup-deletion logSource="pkg/controller/backup_deletion_controller.go:469"
time="2019-07-24T21:01:25Z" level=info msg="Syncing contents of backup store into cluster" backupLocation=default controller=backup-sync logSource="pkg/controller/backup_sync_controller.go:170"
time="2019-07-24T21:01:25Z" level=info msg="Got backups from backup store" backupCount=20 backupLocation=default controller=backup-sync logSource="pkg/controller/backup_sync_controller.go:178"
time="2019-07-24T21:04:25Z" level=error msg="reading plugin stderr" cmd=/plugins/velero-plugin controller=backup-sync error="read |0: file already closed" logSource="pkg/plugin/clientmgmt/logrus_adapter.go:89" pluginName=velero-plugin
time="2019-07-24T21:31:26Z" level=error msg="reading plugin stderr" cmd=/plugins/velero-plugin controller=backup-sync error="read |0: file already closed" logSource="pkg/plugin/clientmgmt/logrus_adapter.go:89" pluginName=velero-plugin
time="2019-07-24T21:34:26Z" level=error msg="reading plugin stderr" cmd=/plugins/velero-plugin controller=backup-sync error="read |0: file already closed" logSource="pkg/plugin/clientmgmt/logrus_adapter.go:89" pluginName=velero-plugin

What did you expect to happen:

Can backup successfully

Environment:

  • Velero version: (use ark version): v1.0.0
  • Kubernetes version: (use kubectl version):
Client Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.9", GitCommit:"16236ce91790d4c75b79f6ce96841db1c843e7d2", GitTreeState:"clean", BuildDate:"2019-03-25T06:40:24Z", GoVersion:"go1.10.8", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"12+", GitVersion:"v1.12.6-aliyun.1", GitCommit:"8cb561c", GitTreeState:"", BuildDate:"2019-04-22T11:34:20Z", GoVersion:"go1.10.8", Compiler:"gc", Platform:"linux/amd64"}
  • Kubernetes installer & version: aliyun
  • Cloud provider or hardware configuration: aliyun
  • OS (e.g. from /etc/os-release): aliyun linux

velero 部署时区为UTC时区,可否提供配置将时区设置为Asia/Shanghai

Describe the solution you'd like
[A clear and concise description of what you want to happen.]
在做定时备份的时候,发现时区为UTC时区,希望试用Asia/Shanghai

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

Environment:

  • Velero version: (use ark version):
    Client:
    Version: v1.1.0
    Git commit: a357f21aec6b39a8244dd23e469cc4519f1fe608
    Server:
    Version: v1.1.0
  • Kubernetes version: (use kubectl version):
    Client Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.0", GitCommit:"641856db18352033a0d96dbc99153fa3b27298e5", GitTreeState:"clean", BuildDate:"2019-03-25T15:53:57Z", GoVersion:"go1.12.1", Compiler:"gc", Platform:"darwin/amd64"}
    Server Version: version.Info{Major:"1", Minor:"14+", GitVersion:"v1.14.6-aliyun.1", GitCommit:"a4182a8", GitTreeState:"", BuildDate:"2019-08-27T06:03:13Z", GoVersion:"go1.12.9", Compiler:"gc", Platform:"linux/amd64"}
  • Kubernetes installer & version:
  • Cloud provider or hardware configuration:
  • OS (e.g. from /etc/os-release):

集群备份失败

What steps did you take and what happened:
[A clear and concise description of what the bug is.]

velero backup后提示成功,但是在restore后发现报错。
velero backup create xxx --snapshot-volumes=false --wait

What did you expect to happen:

正常恢复

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

[root@localhost velero-plugin]# velero restore create --from-backup clusterbk --restore-volumes=false --wait
Restore request "clusterbk-20200107024432" submitted successfully.
Waiting for restore to complete. You may safely press ctrl-c to stop waiting - your restore will continue in the background.
...............................................................
Restore completed with status: Failed. You may check for more information using the commands `velero restore describe clusterbk-20200107024432` and `velero restore logs clusterbk-20200107024432`.
[root@localhost velero-plugin]# velero restore describe clusterbk-20200107024432
Name:         clusterbk-20200107024432
Namespace:    velero
Labels:       <none>
Annotations:  <none>

Phase:  Failed (run 'velero restore logs clusterbk-20200107024432' for more information)

Backup:  clusterbk

Namespaces:
  Included:  *
  Excluded:  <none>

Resources:
  Included:        *
  Excluded:        nodes, events, events.events.k8s.io, backups.velero.io, restores.velero.io, resticrepositories.velero.io
  Cluster-scoped:  auto

Namespace mappings:  <none>

Label selector:  <none>

Restore PVs:  false
[root@localhost velero-plugin]# velero restore logs clusterbk-20200107024432
An error occurred: file not found
[root@localhost velero-plugin]#
[root@localhost velero-plugin]#
[root@localhost velero-plugin]# velero backup get
NAME        STATUS      CREATED                         EXPIRES   STORAGE LOCATION   SELECTOR
clusterbk   Completed   2020-01-06 21:17:22 -0500 EST   29d       default            <none>

Environment:
centos 7.7

  • Velero version: (use ark version):
    1.2
  • Kubernetes version: (use kubectl version):
    1.6.4
  • Kubernetes installer & version:
    rke
  • Cloud provider or hardware configuration:
  • OS (e.g. from /etc/os-release):

Is velero-plugin-alibabacloud:v1.2-991b590 equivalent to velero-plugin-alibabacloud:v1.2

I see that you are using velero-plugin-alibabacloud:v1.2-991b590 as per https://github.com/AliyunContainerService/velero-plugin/blob/master/install/01-velero.yaml#L78.

We have a scenario where we would like to install velero 1.3.0 on Alibaba cluster on china landscape and on Europe landscape.
Can we use velero-plugin-alibabacloud:v1.2 for both landscapes? From our experience velero-plugin-alibabacloud:v1.2 version is not initialized with velero 1.3.0.

Best regards,
Ahmad

Error attempting to get volume ID for persistent volume

time="2019-08-23T00:52:24Z" level=error msg="Error attempting to get volume ID for persistent volume" backup=velero/nginx-backup-volume3 error="rpc error: code = Unknown desc = spec.FlexVolume.Options['VolumeId'] not found" error.file="/Users/hao/go/src/github.com/AliyunContainerService/velero-plugin/pkg/alibabacloud/volume_snapshotter.go:300" error.function=github.com/AliyunContainerService/velero-plugin/pkg/alibabacloud.getEBSDiskID group=v1 logSource="pkg/backup/item_backupper.go:415" name=d-8vb87uf50ubbq62ugrjo namespace=nginx-example persistentVolume=d-8vb87uf50ubbq62ugrjo resource=pods volumeSnapshotLocation=default

在国内阿里云上,使用阿里云的容器服务,运行with-pvc.yaml,查看日志,报如上错误。

Alibabacloud plugin will take action on other cloud

What steps did you take and what happened:
deploy multiple velero plugin in velero

What did you expect to happen:
alibabacloud plugin take no action on other cloud.

Anything else you would like to add:

I write the problem and analysis here:
vmware-tanzu/velero#4256

for Chinese version:
https://velero.cn/d/21-veleroiaas-plugin

Could you delete the RestoreItemAction in alibabacloud plugin? Because the default minimum capacity of disk on Alibabacloud is already 20 Gi. Why you need to change the PV size in the PV restore process ?

Environment:

  • Velero version: (use ark version):1.6.3
  • Kubernetes version: (use kubectl version):1.20.9
  • Kubernetes installer & version:
  • Cloud provider or hardware configuration:
  • OS (e.g. from /etc/os-release):

no matches for kind "BackupStorageLocation" and "VolumeSnapshotLocation"

What steps did you take and what happened:
[A clear and concise description of what the bug is.]
run kubectl apply -f install/velero.yaml
output message end with:
unable to recognize "velero.yaml": no matches for kind "BackupStorageLocation" in version "velero.io/v1"
unable to recognize "velero.yaml": no matches for kind "VolumeSnapshotLocation" in version "velero.io/v1"

What did you expect to happen:
apply success without errors

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

Environment:
aliyun linux

  • Velero version: (use ark version):v1.0.0
  • Kubernetes version: (use kubectl version):v1.15.0
  • Kubernetes installer & version: aliyun
  • Cloud provider or hardware configuration: aliyun
  • OS (e.g. from /etc/os-release): aliyun

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.