VeeamON 2024 - Use Code "COMMUNITY10" for 10% Off!
I have Kasten installed in an OpenStack-Cluster via Helm. I have also set-up an infrastructure profile for OpenStack which is shown as valid. I can run normal Backups /w/o Volume Snapshots just fine but Snapshots fail.The storage class is still recognized as CSI as shown in the Support page. The prefilight checks fail with the following message: ./k10tools primer storage check csiserviceaccount/k10-primer createdclusterrolebinding.rbac.authorization.k8s.io/k10-primer createdjob.batch/k10primer createdPod k10primer-jzvsr is in Pending phasePod Ready!Using "K10_PRIMER_CONFIG_YAML" env var content as config sourceUsing "K10_PRIMER_CONFIG_YAML" env var content as config sourceCSI Snapshot Walkthrough: Unable to find a VolumeSnapshotClass for provisioner (cinder.csi.openstack.org) with k10 annotation (k10.kasten.io/is-snapshot-class) set to true. - ErrorError: {"message":"Unable to find a VolumeSnapshotClass for provisioner (cinder.csi.openstack.org) with k10 annotation (k10.kasten.i
K10 5.5.4 on K3s (stable). All K10 deployments running, all pods also running, all PVCs bound. I was able to create a policy and use it (snapshot, export). Then I deleted that policy. Now no matter what policy settings I choose, “Create policy” button is dimmed and can’t be clicked on to apply.I tried different options including the ones I had before (simple snapshot + export). I also tried creating a policy for different applications - no change, the button is always dimmed. How to troubleshoot this?
when i am describe pod getting below error. Please help me this is important.kubectl describe pod catalog-svc-5847d4fd78-zglgx -n kasten-ioEvents: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Scheduled 9m39s Successfully assigned kasten-io/catalog-svc-5847d4fd78-zglgx to znlapcdp07443v Warning FailedCreatePodSandBox 9m37s kubelet, znlapcdp07443v Failed to create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container "cf03969714a36fbd87688bc756b5e51a3dc89c3a868ace6b8981caf595bc8858" network for pod "catalog-svc-5847d4fd78-zglgx": networkPlugin cni failed to set up pod "catalog-svc-5847d4fd78-zglgx_kasten-io" network: Calico CNI panicked during ADD: runtime error: invalid memory address or nil pointer dereference Normal SandboxChanged
good day, the release notes of v 5.5.2 say that now it’s possible to hide applications from the dasboard by using an Helm flag. https://docs.kasten.io/latest/operating/monitoring.html#k10-compliance Since I’m pretty new to this stuff, I did not understand how can I exclude applications: should I edit a yaml in Openshift for kasten-io project (I’m running on oscp, sure) or shoud I export K10 settings with the command:# helm get values k10 --output yaml --namespace=kasten-io > k10_values.yamlthen edit file file k10_values.yaml adding the Flag and the app names to hide and then reconfigure k10# ??’ how? thanks!!!
HIi try to clean up restore point from GUI, no error but the restore point just wont disappear. i try to do it in command is same result.
HiI try to create new policy and enable snapshot export. i face some error “Profile does not support collections” and i noticed the when i select the export location profile i saw “VBR profiles not permitted here”i checked the location profile for VBR and is valid. anyone have any ideas?
other components like granafa also have this issueWe use rook-ceph as storage class
I just did a reinstall/upgrade of my kasten10 install. Now i get a 404 when trying to connect via portforward… Connection ErrorRequest failed with status code 404 (dashboardbff-svc) i already did:restart my browserkubectl rollout restart deployment -n kasten-io my deployment via fluxcd:---apiVersion: source.toolkit.fluxcd.io/v1beta1kind: HelmRepositorymetadata: name: k10 namespace: flux-systemspec: interval: 10m0s url: https://charts.kasten.io/---apiVersion: helm.toolkit.fluxcd.io/v2beta1kind: HelmReleasemetadata: name: k10 namespace: flux-systemspec: chart: spec: chart: k10 version: 5.5.0 sourceRef: kind: HelmRepository name: k10 interval: 1m0s targetNamespace: kasten-io serviceAccountName: helm-controlleryes all pods are running…kubectl get podsNAME READY STATUS RESTARTS AGEaggregatedapis-svc-656dd6874b-wft9x 1/1 Running 0 11mauth-svc-5dddbc4c8c-b2nvx 1/1 Runnin
Hello, how correct restore application when application is destroy and Kasten application too. How restore application when I haven't Kasten application ? I look how backup Kasten application but there isn't choose for Kasten backup. Thank for answer
Hello.I want to create a new policy that take volumes snapshots without a retention, but I receive the error message “At least one retention value should be non-zero.”Why Kasten gives me this error? I only want to export the snapshots to nfs, not keep them in vSphere.Kasten version: 5.0.10Destination: NFSInfrastructure Profiles: vCenter Server
Hi all,im new to K10 doing POC to check all the features if we will adopt this solution for our needs or not. Have run in this situation, when i'm able to backup apps using pv/pvc, restore them in the same cluster, but unable to restore them in a different cluster with k10restore. Both clusters are setup in the same way, using the same scripts. Each cluster is using different SP to run.Azure setup details:2x AKS: 1.23.8 test1+test2agentpool: 2x Standard_B2mstestnp: 1x Standard_D4ads_v5Using azure CNI in same vnet, different subnetsLocation profile:Locally-redundant storage (LRS)private endpoint in the same vnet as aks clusters Scenario:aks test1:Apps:k10-disaster-recovery-policy backup&snapshot kasten-io namespacedefault-backup backup&snapshot all namespaces (Testapp reside in here) aks test2:storage class createdlocation profile pointing to the same blob storage createdk10-dr-secret createdk10-restore using test1 cluster id and profile name created So far so good.Applications
Hello everyone, I continue to dive into kubernetes and KastenDeployed a new cluster, as a storage system - NetApp OntapDeployed Kasten and a simple applicationI'm trying to make a backup, and the process freezes at the moment of Snapshotting Application Components and nothing happens after that. The task is not interrupted, there are no errors eitherAt the same time, he apparently does the snapshot himself successfullykorp@k8smaster:~$ kubectl get vs -n mysqlNAME READYTOUSE SOURCEPVC SOURCESNAPSHOTCONTENT RESTORESIZE SNAPSHOTCLASS SNAPSHOTCONTENT CREATIONTIME AGEk10-csi-snap-wj6bljvrhrvzblpm false data-my-release-mysql-0 trident-snapshotclass snapcontent-634da5fe-9160-4af1-afb9-d0f9a546d2cd 6m53skorp@k8smaster:~$ kubectl get vsc -n mysqlNAME READYTOUSE RESTORESIZE DELETIONPOL
The catalog server kept on showing me errors after a storage issue yesterday and backups weren’t running anymore. I recreated the catalog DB and Kasten is working again, but I have 500GB + in snapshots that are eating away at my Ceph cluster storage and no easy way to find and delete them. The snaps from Kasten should still be in volumesnapshots and volumesnapshotscontents inside K8.Does anyone have any ideas for me?
I installed in as sandbox environment, all is working but getting ‘unable to validate license’. How do I activate the free 5 node license?
Hello All,I have successfully completed the installation of Kasten-io application.When I run the commands below to see the token information of the service accounts, it does not give any error message, but it does not show the token information either. Has anyone encountered and solved this problem before?kubectl get secret $sa_secret --namespace kasten-io -ojsonpath="{.data.token}{'\n'}" | base64 --decodesa_secret=$(kubectl get serviceaccount my-kasten-sa -o jsonpath="{.secrets[0].name}" --namespace kasten-io)Thanks,Emre ÖZER
Hello, I’m trying to setup an application level backup for MongoDB using kasten/kanister integration in a k8s cluster,i’ve created the Kanister Profile using the Kasten interface for a S3 Compatible target (minIO) ,i’m using this YAML as a base blueprint for the backup action raw.githubusercontent.com/kanisterio/kanister/0.72.0/examples/stable/mongodb/blueprint-v2/mongo-blueprint.yaml when i execute the policy trough kasten UI, i get the following error: cause:cause:cause:fields:- name: messagevalue: "could not render object reference {mongosecret}: template: config:1:14:executing \"config\" at <.Deployment.Name>: can't evaluatefield metadata in type *param.DeploymentParams"Actually our MongoDB is deployed as a Deployment and we have annotated the deployments manifest with this annotation: kanister.kasten.io/blueprint: mongodb-blueprintWhy the kanister operator cannot evaluate correctly the GO template at runtime?
Hello everyone!I’m currently evaluating k10 and having trouble with the generic backup on Longhorn volumes.Pre-flight check returns no errors and I have the same setup in a test cluster which works fine, I’m not sure what the difference is.The Deployment has the the kanister sidecar Pod and the necessary labels and the annotation “k10.kasten.io/forcegenericbackuptrue:true” ist set.Error Message:'{"message":"Failed to backup data","function":"kasten.io/k10/kio/kanister/function.(*backupDataFunc).Exec","linenumber":108,"file":"kasten.io/k10/kio/kanister/function/backup_data.go:108","cause":{"message":"[\"{\\\"message\\\":\\\"Failed to create the backup repository\\\",\\\"function\\\":\\\"kasten.io/k10/kio/kopia.CreateKopiaRepository\\\",\\\"linenumber\\\":470,\\\"file\\\":\\\"kasten.io/k10/kio/kopia/repository.go:470\\\",\\\"cause\\\":{\\\"message\\\":\\\"Failed to exec command in pod: command terminated with exit code 1\\\"}}\",\"{\\\"message\\\":\\\"Failed to connect to the backup repo
Hello,I have a question regarding my snapshots. I have created an NFS location profile. The backups all work fine and the disaster recovery policy works without any problems, but strangely when I download a report it says that I should have 0 snapshots on the storage... also under Data Usage it shows me 0.0B of backups....But funnily enough, I can restore all applications without any problems and they all show up as "Compliant With Policies". Here is a screenshot of my test policy: And here a screenshot of the created folder on the remote storage I don't quite understand whether I don't understand how this works exactly or whether there is a technical issue here... Would a DR be possible at all in this case? Will the data be properly backed up to the remote storage?
I have freshly installed K10 and after the installation Grafana works and after a restart (Of the Cluster or Pod) I get the following error message. Can anyone explain this to me? pod/k10-grafana-856b5d6b5f-nqczn 0/1 Init:CrashLoopBackOffEvents: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Scheduled 32s default-scheduler Successfully assigned kasten-io/k10-grafana-856b5d6b5f-n7x4g to mh-k8s-w3 Warning FailedAttachVolume 32s attachdetach-controller Multi-Attach error for volume "pvc-40666f4b-e505-4e66-9d2d-2cff4090982f" Volume is already exclusively attached to one node and can't be attached to another Normal SuccessfulAttachVolume 30s attachdetach-controller AttachVolume.Attach succeeded for volume "pvc-40666f4b-e505-4e66-9d2d-2cff4090982f" Normal Pulled
Hello! I have a big problem. We had a small network outage in our datacenter and after that I needed to restore an application. I am shocked because my backups seem to be “lost”. After a while of troubleshooting and restarting k10-services, I tried to do a restore and it is working but the export to nfs isnt working. Maybe thats the reason why k10 tells my that there are no restore points for my application. cause: cause: fields: - name: FailedSubPhases value: - Err: cause: cause: cause: cause: cause: message: command terminated with exit code 1 message: invalid repository password file: kasten.io/k10/kio/kopia/repository.go:549 function: kasten.io/k10/kio/kopia.ConnectToKopiaRepository linenumber: 549 message: Failed to connect to the backup repository
Hello, I am deploying Kasten on an old version of Openshift (above 4.0.5 is not working because of the Kubernetes version). When trying to install Kasten with Kanister sidecar injection, I get the following error:Error: INSTALLATION FAILED: unable to build kubernetes objects from release manifest: error validating "": error validating data: [ValidationError(MutatingWebhookConfiguration.webhooks[0].clientConfig.service): unknown field "port" in io.k8s.api.admissionregistration.v1beta1.ServiceReference, ValidationError(MutatingWebhookConfiguration.webhooks[0]): unknown field "sideEffects" in io.k8s.api.admissionregistration.v1beta1.Webhook] I tried different helm installation parameters and my last version is the following (using https://docs.kasten.io/4.0.2/install/advanced.html as reference): helm install k10 kasten/k10 --namespace=kasten-io \ --set metering.mode=airgap \ --set auth.tokenAuth.enabled=true \ --set cacertconfigmap.name="custom-cert" \ --set injectKanisterSide
Hi!I have problems with using a blueprint to backup a mariadb deployment in kubernetes. After running trough a series of error messages I made ot to the last that did not let me successful back up the workload with a blueprint: cause: cause: fields: - name: message value: 'Failed while waiting for Pod kanister-job-t8pw4 to complete: Pod failed or did not transition into complete state: Pod kanister-job-t8pw4 failed. Pod details (&Pod{ObjectMeta:{kanister-job-t8pw4 kanister-job- APPNAME-CUSTOMER-test 754772e9-403e-447e-8c4a-d6a6f3dbe006 42480080 0 2022-04-29 09:55:17 +0000 UTC <nil> <nil> map[createdBy:kanister] map[cni.projectcalico.org/containerID:ab374f1fc96af0c13fd75443989d41e27533a3fc5cf85e8c4fee40dc8996a748 cni.projectcalico.org/podIP: cni.projectcalico.org/podIPs:] [] [] [{Go-http-client Update v1 2022-04-29 09:55:17 +0000 UTC FieldsV1 {"f:metadata":{"f:generateName":{},"f:l
Hello,I’ve upgraded from 4.5.10 to 4.5.13 this week, since then my backups are failing.Looks like there is a new ambassador version since 4.5.12, which can’t be pulled (Back-off pulling image "quay.io/datawire/ambassador:2.2.2")Can’t find that image version on the quay.io registry. Is this a known issue?
Hi Team,I am trying to import a backup from a CEPH bucket but I am getting the below error. cause: cause: message: "[POST /artifacts:getOrAdd][409] getOrAddArtifactConflict &{Message:}" fields: - name: artifactID value: 98b03f70-9948-11ec-bd13-0a580a800571 function: kasten.io/k10/kio/exec/phases/phase.(*migrateReceivePhase).importArtifact linenumber: 783 message: failed to import Manifest artifactmessage: Job failed to be executedfields: []Kasten version 4.5.3 Kubernetes Version v1.21.6+c180a7c Kubernetes Release Type OpenShift Can you please help in solving the error?Regards
Hi.Doesn anyone know how using Kasten Helm chart (4.5.9) to influence/change default kanister-sidecar behavior?So far I wasn’t able to deploy it as sidecar in any namespace with limits set (without patching deployments ot statefullsets).Kanister-sidecar attaches properly to any deployment in namespace without limits, and I am unable to find an easy way to to change its resources.Did a little bit tweaking of prod-spec-override, but it seems it’s for different purposes
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
