Hello! I try to backup a namespace containing a deployment with the following resources: deployments, service, configmap, secrets, pvc/pv (storageclass rook and nfs). It seems that I have problems with the nfs storageclass: If I try to backup every ressource I get an error “storageclass not supported”. Thats no problem I thought, because I tried: Excluding the pvc by name in the policy. But it got stuck in the phase “Snapshotting Application Components” Can you help me out with this, its freaking me out. Kubernetes 1.22 fresh installed K10 4.5.9

Okay it seems that I can snapshot again. Thanks a lot guys. I used the tools kubestr and the tools from the prerequisites to check anything.What I did:I downloaded again the files from the external-snapshotterhttps://github.com/kubernetes-csi/external-snapshotter(Just ignored anything except the “headings”Install Snapshot CRDsInstall Common Snapshot ControllerI deleted the deployed components with kubectl delete -f (snapshot crd AND snapshot-controller)I installed the snapshot CRDs i uninstalled in step 1 (but with kubectl apply -f crd/ not kubectl kustomize crd/ | kubectl apply -f - (that made problems)installed the snapshot controller uninstalled in step 1 (same here, just kubectl apply -f .I downloaded again the snapshotclass-yamls vor cephfs and rbdhttps://github.com/rook/rook/tree/master/deploy/examples/csiand applied them. Dont forget to add the annotations for k10 again!https://docs.kasten.io/latest/install/storage.html#csi-snapshot-configurationAfter that I retested my setup with kubestr and the prerequisites tool →DONE and OK!Tomorrow I will test the restore.Thanks a lot again to everyone. Have a nice evening

You made me unsure about the deployment of the volumesnapshotclass, but I have deployed it from this Documentation.Details:Rook-Ceph 1.7.4Ubuntu 20.04.3 LTS newest UpdatesKubernetes 1.22.2Containerd 1.4.12What about the deprecation message? Could this be a problem? How do you guys install the external-snapshotter? And which version? I can also post my volumesnapshotclasses if needed.

Solved

Policy fails or got stuck in "Snapshotting Application Components"

3 years ago
February 17, 2022
9 comments
1786 views

SMT-Almato
Comes here often
19 comments

Hello!

I try to backup a namespace containing a deployment with the following resources:

deployments, service, configmap, secrets, pvc/pv (storageclass rook and nfs). It seems that I have problems with the nfs storageclass:

If I try to backup every ressource I get an error “storageclass not supported”. Thats no problem I thought, because I tried:
Excluding the pvc by name in the policy. But it got stuck in the phase “Snapshotting Application Components”

Can you help me out with this, its freaking me out.

Kubernetes 1.22

fresh installed K10 4.5.9

Best answer by SMT-Almato

Okay it seems that I can snapshot again. Thanks a lot guys. I used the tools kubestr and the tools from the prerequisites to check anything.

What I did:

I downloaded again the files from the external-snapshotter https://github.com/kubernetes-csi/external-snapshotter (Just ignored anything except the “headings”
- Install Snapshot CRDs
- Install Common Snapshot Controller
I deleted the deployed components with kubectl delete -f (snapshot crd AND snapshot-controller)
I installed the snapshot CRDs i uninstalled in step 1 (but with kubectl apply -f crd/ not kubectl kustomize crd/ | kubectl apply -f - (that made problems)
installed the snapshot controller uninstalled in step 1 (same here, just kubectl apply -f .
I downloaded again the snapshotclass-yamls vor cephfs and rbd https://github.com/rook/rook/tree/master/deploy/examples/csi and applied them. Dont forget to add the annotations for k10 again! https://docs.kasten.io/latest/install/storage.html#csi-snapshot-configuration

After that I retested my setup with kubestr and the prerequisites tool → DONE and OK!

Tomorrow I will test the restore.

Thanks a lot again to everyone. Have a nice evening

View original

Did this topic help you find an answer to your question?

AdamBergh
Comes here often
11 comments
3 years ago
February 17, 2022

Hi, thanks for posting in the forums. Can you post some more details about your storageclass? Is it a CSI based storage class? Can you post the output of “kubectl get sc” command?

If it’s a CSI based storageclass can you test the CSI with the opensource tool “kubestr” https://kubestr.io/

Run ./kubestr csicheck -s <storage class> -v <volume snapshot class>
and post the results?

temrich
Not a newbie anymore
1 comment
3 years ago
February 17, 2022

Rather than excluding the storageclass PVCs, why not configure it so it can snapshot?
Before you deployed Kasten, did you run the pre-flight/primer script to validate that your storageclass and snapshotclass is setup?
curl https://docs.kasten.io/tools/k10_primer.sh | bash

You can harmlessly run it after you’ve already deployed which will temporarily create a small pod and PVC on each storageclass, snapshot it, and then delete it. You should get all ‘OK’.

SMT-Almato
Author
Comes here often
19 comments
3 years ago
February 17, 2022

At first, thanks a lot for the response.

AdamBergh wrote:

I did the steps you told me, here are the results:

# kubectl get sc
NAME              PROVISIONER                     RECLAIMPOLICY   VOLUMEBINDINGMODE   ALLOWVOLUMEEXPANSION   AGE
rook-ceph-block   rook-ceph.rbd.csi.ceph.com      Retain          Immediate           true                   133d
rook-cephfs       rook-ceph.cephfs.csi.ceph.com   Retain          Immediate           false                  120d

# kubectl get volumesnapshotclasses.snapshot.storage.k8s.io
NAME                                DRIVER                          DELETIONPOLICY   AGE
csi-cephfsplugin-snapclass          rook-ceph.cephfs.csi.ceph.com   Delete           77d
csi-rbdplugin-snapclass             rook-ceph.rbd.csi.ceph.com      Delete           77d
k10-clone-csi-rbdplugin-snapclass   rook-ceph.rbd.csi.ceph.com      Retain           5d22h

And I tried to do a snapshot with kubestr (wow I didnt know that!) - but that result is very confusing, because I was able to snapshot before in this cluster:

Hide contentShow content

# ./kubestr csicheck -s rook-ceph-block -v csi-rbdplugin-snapclass
Creating application
  -> Created pod (kubestr-csi-original-podnvtt6) and pvc (kubestr-csi-original-pvcghwh5)
Taking a snapshot
W0217 15:51:13.311990 2735423 warnings.go:70] snapshot.storage.k8s.io/v1beta1 VolumeSnapshot is deprecated; use snapshot.storage.k8s.io/v1 VolumeSnapshot
W0217 15:51:13.315896 2735423 warnings.go:70] snapshot.storage.k8s.io/v1beta1 VolumeSnapshot is deprecated; use snapshot.storage.k8s.io/v1 VolumeSnapshot
W0217 15:51:13.422809 2735423 warnings.go:70] snapshot.storage.k8s.io/v1beta1 VolumeSnapshot is deprecated; use snapshot.storage.k8s.io/v1 VolumeSnapshot
W0217 15:51:13.631012 2735423 warnings.go:70] snapshot.storage.k8s.io/v1beta1 VolumeSnapshot is deprecated; use snapshot.storage.k8s.io/v1 VolumeSnapshot
W0217 15:51:14.039533 2735423 warnings.go:70] snapshot.storage.k8s.io/v1beta1 VolumeSnapshot is deprecated; use snapshot.storage.k8s.io/v1 VolumeSnapshot
W0217 15:51:14.846969 2735423 warnings.go:70] snapshot.storage.k8s.io/v1beta1 VolumeSnapshot is deprecated; use snapshot.storage.k8s.io/v1 VolumeSnapshot
W0217 15:51:16.451813 2735423 warnings.go:70] snapshot.storage.k8s.io/v1beta1 VolumeSnapshot is deprecated; use snapshot.storage.k8s.io/v1 VolumeSnapshot
W0217 15:51:19.660208 2735423 warnings.go:70] snapshot.storage.k8s.io/v1beta1 VolumeSnapshot is deprecated; use snapshot.storage.k8s.io/v1 VolumeSnapshot
W0217 15:51:26.069289 2735423 warnings.go:70] snapshot.storage.k8s.io/v1beta1 VolumeSnapshot is deprecated; use snapshot.storage.k8s.io/v1 VolumeSnapshot
W0217 15:51:36.078166 2735423 warnings.go:70] snapshot.storage.k8s.io/v1beta1 VolumeSnapshot is deprecated; use snapshot.storage.k8s.io/v1 VolumeSnapshot
W0217 15:51:46.083772 2735423 warnings.go:70] snapshot.storage.k8s.io/v1beta1 VolumeSnapshot is deprecated; use snapshot.storage.k8s.io/v1 VolumeSnapshot
W0217 15:51:56.093316 2735423 warnings.go:70] snapshot.storage.k8s.io/v1beta1 VolumeSnapshot is deprecated; use snapshot.storage.k8s.io/v1 VolumeSnapshot
W0217 15:52:06.103094 2735423 warnings.go:70] snapshot.storage.k8s.io/v1beta1 VolumeSnapshot is deprecated; use snapshot.storage.k8s.io/v1 VolumeSnapshot
W0217 15:52:16.112038 2735423 warnings.go:70] snapshot.storage.k8s.io/v1beta1 VolumeSnapshot is deprecated; use snapshot.storage.k8s.io/v1 VolumeSnapshot
W0217 15:52:26.119802 2735423 warnings.go:70] snapshot.storage.k8s.io/v1beta1 VolumeSnapshot is deprecated; use snapshot.storage.k8s.io/v1 VolumeSnapshot
W0217 15:52:36.129545 2735423 warnings.go:70] snapshot.storage.k8s.io/v1beta1 VolumeSnapshot is deprecated; use snapshot.storage.k8s.io/v1 VolumeSnapshot
W0217 15:52:46.137038 2735423 warnings.go:70] snapshot.storage.k8s.io/v1beta1 VolumeSnapshot is deprecated; use snapshot.storage.k8s.io/v1 VolumeSnapshot
W0217 15:52:56.144451 2735423 warnings.go:70] snapshot.storage.k8s.io/v1beta1 VolumeSnapshot is deprecated; use snapshot.storage.k8s.io/v1 VolumeSnapshot
W0217 15:53:06.151079 2735423 warnings.go:70] snapshot.storage.k8s.io/v1beta1 VolumeSnapshot is deprecated; use snapshot.storage.k8s.io/v1 VolumeSnapshot
W0217 15:53:16.156926 2735423 warnings.go:70] snapshot.storage.k8s.io/v1beta1 VolumeSnapshot is deprecated; use snapshot.storage.k8s.io/v1 VolumeSnapshot
W0217 15:53:26.164965 2735423 warnings.go:70] snapshot.storage.k8s.io/v1beta1 VolumeSnapshot is deprecated; use snapshot.storage.k8s.io/v1 VolumeSnapshot
W0217 15:53:36.172647 2735423 warnings.go:70] snapshot.storage.k8s.io/v1beta1 VolumeSnapshot is deprecated; use snapshot.storage.k8s.io/v1 VolumeSnapshot
W0217 15:53:46.179755 2735423 warnings.go:70] snapshot.storage.k8s.io/v1beta1 VolumeSnapshot is deprecated; use snapshot.storage.k8s.io/v1 VolumeSnapshot
W0217 15:53:56.187954 2735423 warnings.go:70] snapshot.storage.k8s.io/v1beta1 VolumeSnapshot is deprecated; use snapshot.storage.k8s.io/v1 VolumeSnapshot
W0217 15:54:06.196652 2735423 warnings.go:70] snapshot.storage.k8s.io/v1beta1 VolumeSnapshot is deprecated; use snapshot.storage.k8s.io/v1 VolumeSnapshot
W0217 15:54:16.202623 2735423 warnings.go:70] snapshot.storage.k8s.io/v1beta1 VolumeSnapshot is deprecated; use snapshot.storage.k8s.io/v1 VolumeSnapshot
W0217 15:54:26.211196 2735423 warnings.go:70] snapshot.storage.k8s.io/v1beta1 VolumeSnapshot is deprecated; use snapshot.storage.k8s.io/v1 VolumeSnapshot
W0217 15:54:36.219797 2735423 warnings.go:70] snapshot.storage.k8s.io/v1beta1 VolumeSnapshot is deprecated; use snapshot.storage.k8s.io/v1 VolumeSnapshot
W0217 15:54:46.227486 2735423 warnings.go:70] snapshot.storage.k8s.io/v1beta1 VolumeSnapshot is deprecated; use snapshot.storage.k8s.io/v1 VolumeSnapshot
W0217 15:54:56.234949 2735423 warnings.go:70] snapshot.storage.k8s.io/v1beta1 VolumeSnapshot is deprecated; use snapshot.storage.k8s.io/v1 VolumeSnapshot
W0217 15:55:06.244241 2735423 warnings.go:70] snapshot.storage.k8s.io/v1beta1 VolumeSnapshot is deprecated; use snapshot.storage.k8s.io/v1 VolumeSnapshot
W0217 15:55:16.255023 2735423 warnings.go:70] snapshot.storage.k8s.io/v1beta1 VolumeSnapshot is deprecated; use snapshot.storage.k8s.io/v1 VolumeSnapshot
W0217 15:55:26.263142 2735423 warnings.go:70] snapshot.storage.k8s.io/v1beta1 VolumeSnapshot is deprecated; use snapshot.storage.k8s.io/v1 VolumeSnapshot
W0217 15:55:36.305102 2735423 warnings.go:70] snapshot.storage.k8s.io/v1beta1 VolumeSnapshot is deprecated; use snapshot.storage.k8s.io/v1 VolumeSnapshot
W0217 15:55:46.395523 2735423 warnings.go:70] snapshot.storage.k8s.io/v1beta1 VolumeSnapshot is deprecated; use snapshot.storage.k8s.io/v1 VolumeSnapshot
W0217 15:55:56.464577 2735423 warnings.go:70] snapshot.storage.k8s.io/v1beta1 VolumeSnapshot is deprecated; use snapshot.storage.k8s.io/v1 VolumeSnapshot
Cleaning up resources
Error deleteing PVC (kubestr-csi-original-pvcghwh5) - (context deadline exceeded)
Error deleteing Pod (kubestr-csi-original-podnvtt6) - (context deadline exceeded)
CSI checker test:
  Failed to create Snapshot: CSI Driver failed to create snapshot for PVC (kubestr-csi-original-pvcghwh5) in Namespace (default): context deadline exceeded  -  Error
Error: Failed to create Snapshot: CSI Driver failed to create snapshot for PVC (kubestr-csi-original-pvcghwh5) in Namespace (default): context deadline exceeded

# ./kubestr csicheck -s rook-cephfs -v csi-cephfsplugin-snapclass
Creating application
  -> Created pod (kubestr-csi-original-pod7gwlw) and pvc (kubestr-csi-original-pvccmc7w)
Taking a snapshot
W0217 15:55:06.891768 2738647 warnings.go:70] snapshot.storage.k8s.io/v1beta1 VolumeSnapshot is deprecated; use snapshot.storage.k8s.io/v1 VolumeSnapshot
W0217 15:55:06.897166 2738647 warnings.go:70] snapshot.storage.k8s.io/v1beta1 VolumeSnapshot is deprecated; use snapshot.storage.k8s.io/v1 VolumeSnapshot
W0217 15:55:07.003951 2738647 warnings.go:70] snapshot.storage.k8s.io/v1beta1 VolumeSnapshot is deprecated; use snapshot.storage.k8s.io/v1 VolumeSnapshot
W0217 15:55:07.212543 2738647 warnings.go:70] snapshot.storage.k8s.io/v1beta1 VolumeSnapshot is deprecated; use snapshot.storage.k8s.io/v1 VolumeSnapshot
W0217 15:55:07.621382 2738647 warnings.go:70] snapshot.storage.k8s.io/v1beta1 VolumeSnapshot is deprecated; use snapshot.storage.k8s.io/v1 VolumeSnapshot
W0217 15:55:08.429881 2738647 warnings.go:70] snapshot.storage.k8s.io/v1beta1 VolumeSnapshot is deprecated; use snapshot.storage.k8s.io/v1 VolumeSnapshot
W0217 15:55:10.039832 2738647 warnings.go:70] snapshot.storage.k8s.io/v1beta1 VolumeSnapshot is deprecated; use snapshot.storage.k8s.io/v1 VolumeSnapshot
W0217 15:55:13.251270 2738647 warnings.go:70] snapshot.storage.k8s.io/v1beta1 VolumeSnapshot is deprecated; use snapshot.storage.k8s.io/v1 VolumeSnapshot
W0217 15:55:19.658110 2738647 warnings.go:70] snapshot.storage.k8s.io/v1beta1 VolumeSnapshot is deprecated; use snapshot.storage.k8s.io/v1 VolumeSnapshot
W0217 15:55:29.667467 2738647 warnings.go:70] snapshot.storage.k8s.io/v1beta1 VolumeSnapshot is deprecated; use snapshot.storage.k8s.io/v1 VolumeSnapshot
W0217 15:55:39.675802 2738647 warnings.go:70] snapshot.storage.k8s.io/v1beta1 VolumeSnapshot is deprecated; use snapshot.storage.k8s.io/v1 VolumeSnapshot
W0217 15:55:49.684160 2738647 warnings.go:70] snapshot.storage.k8s.io/v1beta1 VolumeSnapshot is deprecated; use snapshot.storage.k8s.io/v1 VolumeSnapshot
W0217 15:55:59.689491 2738647 warnings.go:70] snapshot.storage.k8s.io/v1beta1 VolumeSnapshot is deprecated; use snapshot.storage.k8s.io/v1 VolumeSnapshot
W0217 15:56:09.699053 2738647 warnings.go:70] snapshot.storage.k8s.io/v1beta1 VolumeSnapshot is deprecated; use snapshot.storage.k8s.io/v1 VolumeSnapshot
W0217 15:56:19.707850 2738647 warnings.go:70] snapshot.storage.k8s.io/v1beta1 VolumeSnapshot is deprecated; use snapshot.storage.k8s.io/v1 VolumeSnapshot
W0217 15:56:29.716532 2738647 warnings.go:70] snapshot.storage.k8s.io/v1beta1 VolumeSnapshot is deprecated; use snapshot.storage.k8s.io/v1 VolumeSnapshot
W0217 15:56:39.725650 2738647 warnings.go:70] snapshot.storage.k8s.io/v1beta1 VolumeSnapshot is deprecated; use snapshot.storage.k8s.io/v1 VolumeSnapshot
W0217 15:56:49.735800 2738647 warnings.go:70] snapshot.storage.k8s.io/v1beta1 VolumeSnapshot is deprecated; use snapshot.storage.k8s.io/v1 VolumeSnapshot
W0217 15:56:59.742327 2738647 warnings.go:70] snapshot.storage.k8s.io/v1beta1 VolumeSnapshot is deprecated; use snapshot.storage.k8s.io/v1 VolumeSnapshot
W0217 15:57:09.749681 2738647 warnings.go:70] snapshot.storage.k8s.io/v1beta1 VolumeSnapshot is deprecated; use snapshot.storage.k8s.io/v1 VolumeSnapshot
W0217 15:57:19.758370 2738647 warnings.go:70] snapshot.storage.k8s.io/v1beta1 VolumeSnapshot is deprecated; use snapshot.storage.k8s.io/v1 VolumeSnapshot
W0217 15:57:29.767042 2738647 warnings.go:70] snapshot.storage.k8s.io/v1beta1 VolumeSnapshot is deprecated; use snapshot.storage.k8s.io/v1 VolumeSnapshot
W0217 15:57:39.775866 2738647 warnings.go:70] snapshot.storage.k8s.io/v1beta1 VolumeSnapshot is deprecated; use snapshot.storage.k8s.io/v1 VolumeSnapshot
W0217 15:57:49.784889 2738647 warnings.go:70] snapshot.storage.k8s.io/v1beta1 VolumeSnapshot is deprecated; use snapshot.storage.k8s.io/v1 VolumeSnapshot
W0217 15:57:59.790779 2738647 warnings.go:70] snapshot.storage.k8s.io/v1beta1 VolumeSnapshot is deprecated; use snapshot.storage.k8s.io/v1 VolumeSnapshot
W0217 15:58:09.800326 2738647 warnings.go:70] snapshot.storage.k8s.io/v1beta1 VolumeSnapshot is deprecated; use snapshot.storage.k8s.io/v1 VolumeSnapshot
W0217 15:58:19.807163 2738647 warnings.go:70] snapshot.storage.k8s.io/v1beta1 VolumeSnapshot is deprecated; use snapshot.storage.k8s.io/v1 VolumeSnapshot
W0217 15:58:29.813993 2738647 warnings.go:70] snapshot.storage.k8s.io/v1beta1 VolumeSnapshot is deprecated; use snapshot.storage.k8s.io/v1 VolumeSnapshot
W0217 15:58:39.820539 2738647 warnings.go:70] snapshot.storage.k8s.io/v1beta1 VolumeSnapshot is deprecated; use snapshot.storage.k8s.io/v1 VolumeSnapshot
W0217 15:58:49.827020 2738647 warnings.go:70] snapshot.storage.k8s.io/v1beta1 VolumeSnapshot is deprecated; use snapshot.storage.k8s.io/v1 VolumeSnapshot
W0217 15:58:59.835054 2738647 warnings.go:70] snapshot.storage.k8s.io/v1beta1 VolumeSnapshot is deprecated; use snapshot.storage.k8s.io/v1 VolumeSnapshot
W0217 15:59:09.845939 2738647 warnings.go:70] snapshot.storage.k8s.io/v1beta1 VolumeSnapshot is deprecated; use snapshot.storage.k8s.io/v1 VolumeSnapshot
W0217 15:59:19.854794 2738647 warnings.go:70] snapshot.storage.k8s.io/v1beta1 VolumeSnapshot is deprecated; use snapshot.storage.k8s.io/v1 VolumeSnapshot
W0217 15:59:29.865873 2738647 warnings.go:70] snapshot.storage.k8s.io/v1beta1 VolumeSnapshot is deprecated; use snapshot.storage.k8s.io/v1 VolumeSnapshot
W0217 15:59:39.872925 2738647 warnings.go:70] snapshot.storage.k8s.io/v1beta1 VolumeSnapshot is deprecated; use snapshot.storage.k8s.io/v1 VolumeSnapshot
W0217 15:59:49.883394 2738647 warnings.go:70] snapshot.storage.k8s.io/v1beta1 VolumeSnapshot is deprecated; use snapshot.storage.k8s.io/v1 VolumeSnapshot
Cleaning up resources
Error deleteing PVC (kubestr-csi-original-pvccmc7w) - (context deadline exceeded)
Error deleteing Pod (kubestr-csi-original-pod7gwlw) - (context deadline exceeded)
CSI checker test:
  Failed to create Snapshot: CSI Driver failed to create snapshot for PVC (kubestr-csi-original-pvccmc7w) in Namespace (default): context deadline exceeded  -  Error
Error: Failed to create Snapshot: CSI Driver failed to create snapshot for PVC (kubestr-csi-original-pvccmc7w) in Namespace (default): context deadline exceeded

temrich wrote:

You can harmlessly run it after you’ve already deployed which will temporarily create a small pod and PVC on each storageclass, snapshot it, and then delete it. You should get all ‘OK’.

I did this before installing k10 - the results seemed okay to me (I googled “Missing/Failed to Fetch CSIDriver Object” - but that shouldn’t be a problem according to kasten-io.

Hide contentShow content

Checking for tools
 --> Found kubectl
 --> Found helm
Checking if the Kasten Helm repo is present
 --> The Kasten Helm repo was found
Checking for required Helm version (>= v3.0.0)
 --> No Tiller needed with Helm v3.8.0
K10Primer image
 --> Using Image (gcr.io/kasten-images/k10tools:4.5.9) to run test
Checking access to the Kubernetes context kubernetes-admin@kubernetes
 --> Able to access the default Kubernetes namespace
K10 Kanister tools image
 --> Using Kanister tools image (ghcr.io/kanisterio/kanister-tools:0.73.0) to run test

Running K10Primer Job in cluster with command-
     ./k10tools primer
serviceaccount/k10-primer created
clusterrolebinding.rbac.authorization.k8s.io/k10-primer created
job.batch/k10primer created
Waiting for pod k10primer--1-cdvkh to be ready - ContainerCreating
Waiting for pod k10primer--1-cdvkh to be ready - ContainerCreating
Waiting for pod k10primer--1-cdvkh to be ready - ContainerCreating
Waiting for pod k10primer--1-cdvkh to be ready - ContainerCreating
Waiting for pod k10primer--1-cdvkh to be ready - ContainerCreating
Waiting for pod k10primer--1-cdvkh to be ready - ContainerCreating
Waiting for pod k10primer--1-cdvkh to be ready - ContainerCreating
Pod Ready!

Kubernetes Version Check:
  Valid kubernetes version (v1.22.0)  -  OK

RBAC Check:
  Kubernetes RBAC is enabled  -  OK

Aggregated Layer Check:
  The Kubernetes Aggregated Layer is enabled  -  OK

         Found multiple snapshot API group versions, using preferred.
CSI Capabilities Check:
  Using CSI GroupVersion snapshot.storage.k8s.io/v1  -  OK

         Found multiple snapshot API group versions, using preferred.
I0217 14:55:46.550548       8 request.go:665] Waited for 1.046794033s due to client-side throttling, not priority and fairness, request: GET:https://10.96.0.1:443/apis/autoscaling/v1
         Found multiple snapshot API group versions, using preferred.
Validating Provisioners:
rook-ceph.rbd.csi.ceph.com:
  Is a CSI Provisioner  -  OK
  Missing/Failed to Fetch CSIDriver Object
  Storage Classes:
    rook-ceph-block
      Valid Storage Class  -  OK
  Volume Snapshot Classes:
    csi-rbdplugin-snapclass
      Has k10.kasten.io/is-snapshot-class annotation set to true  -  OK
      Has deletionPolicy 'Delete'  -  OK
    k10-clone-csi-rbdplugin-snapclass

rook-ceph.cephfs.csi.ceph.com:
  Is a CSI Provisioner  -  OK
  Missing/Failed to Fetch CSIDriver Object
  Storage Classes:
    rook-cephfs
      Valid Storage Class  -  OK
  Volume Snapshot Classes:
    csi-cephfsplugin-snapclass
      Has k10.kasten.io/is-snapshot-class annotation set to true  -  OK
      Has deletionPolicy 'Delete'  -  OK

Validate Generic Volume Snapshot:
  Pod Created successfully  -  OK
  GVS Backup command executed successfully  -  OK
  Pod deleted successfully  -  OK

serviceaccount "k10-primer" deleted
clusterrolebinding.rbac.authorization.k8s.io "k10-primer" deleted
job.batch "k10primer" deleted

additionially, I have to say, that I dont use a Snapshotclass for the nfs mount. Let me show the yaml to this:

---
  apiVersion: v1
  kind: PersistentVolume
  metadata:
    name: pv-k10-backup
  spec:
    storageClassName: ""
    capacity:
      storage: 1024Gi
    accessModes:
      - ReadWriteOnce
    claimRef:
      namespace: kasten-io
      name: pvc-k10-backup
    nfs:
      server: <IP-TO-NFS-SERVER>
      path: "/vol/backup/k10/"

---
  apiVersion: v1
  kind: PersistentVolumeClaim
  metadata:
    name: pvc-k10-backup
    namespace: kasten-io
  spec:
    accessModes:
      - ReadWriteOnce
    storageClassName: ""
    resources:
      requests:
        storage: 1024Gi

Thanks a lot!

AdamBergh
Comes here often
11 comments
3 years ago
February 17, 2022

Kubestr tests the same behavior as Kasten K10 - meaning that if Kubestr fails, Kasten will as well. Rook/Ceph should support volumesnapshot capability as documented here: https://github.com/rook/rook/blob/master/Documentation/ceph-csi-snapshot.md

Can you confirm your volumesnapshot class is set up as in this documentation? Also can you provide the Kubernetes version and distro you are running?

It’s also possible to set up Kasten K10 to use “generic” backup - bypassing the CSI snapshot functionality - see https://docs.kasten.io/latest/install/generic.html

SMT-Almato
Author
Comes here often
19 comments
3 years ago
February 17, 2022

You made me unsure about the deployment of the volumesnapshotclass, but I have deployed it from this Documentation.

Details:

Rook-Ceph 1.7.4
Ubuntu 20.04.3 LTS newest Updates
Kubernetes 1.22.2
Containerd 1.4.12

What about the deprecation message? Could this be a problem? How do you guys install the external-snapshotter? And which version? I can also post my volumesnapshotclasses if needed.

+22

Geoff Burke
Veeam Legend, Veeam Vanguard
1317 comments
3 years ago
February 17, 2022

SMT-Almato wrote:

You made me unsure about the deployment of the volumesnapshotclass, but I have deployed it from this Documentation.

Details:

Rook-Ceph 1.7.4
Ubuntu 20.04.3 LTS newest Updates
Kubernetes 1.22.2
Containerd 1.4.12

What about the deprecation message? Could this be a problem? How do you guys install the external-snapshotter? And which version? I can also post my volumesnapshotclasses if needed.

I got stuck on this with Rook/Ceph as well. If I remember correctly I used the these instructions in git hub:

https://github.com/kubernetes-csi/external-snapshotter

VMCA2024, VMCE2023, VMCE2024-SP,CKA, LFCS, PCA,TARS

+22

Geoff Burke
Veeam Legend, Veeam Vanguard
1317 comments
3 years ago
February 17, 2022

Although it has a snapshotclass which mine would not allow me to apply the manifest in rook because the I was missing the snapshoter. I did once for some reason lack a snapshotcontroller once, so might be a good idea to go over the github stuff just in case.

VMCA2024, VMCE2023, VMCE2024-SP,CKA, LFCS, PCA,TARS

SMT-Almato
Author
Comes here often
19 comments
Answer
3 years ago
February 17, 2022

Okay it seems that I can snapshot again. Thanks a lot guys. I used the tools kubestr and the tools from the prerequisites to check anything.

What I did:

I downloaded again the files from the external-snapshotter https://github.com/kubernetes-csi/external-snapshotter (Just ignored anything except the “headings”
- Install Snapshot CRDs
- Install Common Snapshot Controller
I deleted the deployed components with kubectl delete -f (snapshot crd AND snapshot-controller)
I installed the snapshot CRDs i uninstalled in step 1 (but with kubectl apply -f crd/ not kubectl kustomize crd/ | kubectl apply -f - (that made problems)
installed the snapshot controller uninstalled in step 1 (same here, just kubectl apply -f .
I downloaded again the snapshotclass-yamls vor cephfs and rbd https://github.com/rook/rook/tree/master/deploy/examples/csi and applied them. Dont forget to add the annotations for k10 again! https://docs.kasten.io/latest/install/storage.html#csi-snapshot-configuration

After that I retested my setup with kubestr and the prerequisites tool → DONE and OK!

Tomorrow I will test the restore.

Thanks a lot again to everyone. Have a nice evening

Madhuri
Comes here often
11 comments
2 years ago
August 23, 2022

Hi , I’m facing the similar issue-

curl -s https://docs.kasten.io/tools/k10_primer.sh | bash - Looks all ok.

Validate Generic Volume Snapshot:
Pod created successfully - OK
GVS Backup command executed successfully - OK
Pod deleted successfully - OK

Here is the output of - kubectl get sc command

root@k8s-masterk10:~# kubectl get sc
NAME PROVISIONER RECLAIMPOLICY VOLUMEBINDINGMODE ALLOWVOLUMEEXPANSION AGE
standard (default) k8s.io/minikube-hostpath Delete Immediate false 11d
root@k8s-masterk10:~#

Please suggest.

Comment

Related topics

Mais uma situação inusitada com a NOSicon

Contestação da Factura NOSicon

Devolução Equipamento na adesão à NOSicon

Preciso regularizar a minha situaçãoicon

Serviço de apoio ao cliente miserável. Não resolvem a situação, quando se comprometeram.icon

Sign up

Login to the community

Scanning file for viruses.

This file cannot be downloaded