VeeamON 2024 - Use Code "COMMUNITY10" for 10% Off!
@WWK-Cloud-Plattform if could guess whic RBAC is missing if you share the role/clusterrole assinged to that user.BR,Ahmed Hagag
@WWK-Cloud-Plattform what is your k10 version?This issue is fixed in k10 v 6.5.0, please upgrade to that version.BR,Ahmed Hagag
@virtualhobbit w fixed an issue where applications restore was failing on vSphere Tanzu 8.0U2.please try to upgrade to k10 v 6.5.0 and try again. ThanksAhmed Hagag
Hi @Florian Lacrampe so to get your question well, You cannot access the gcr.io/kasten-io repository directly and you would like to use k10offline to list images for Kasten version 6.5.0?in the doc you are sharing, in order to list the images you should have access to “gcr.io/kasten-images/k10offline” either by setting up a caching or proxy image registry that points to the Kasten K10 image repositories or manually/automatically uploading the images to your private registry. docker run --rm -it gcr.io/kasten-images/k10offline:6.5.0 list-images
@Florian Lacrampe Did you download the k10 6.5.0 images and move them to your private repo?I see you are trying to list the images using your local_registry_urlfirst, you need to download, tag, and move images to your private registry.ThanksAhmed Hagag
@Daniel Moes What was your old k10 version? fine? Have there been any changes in your cluster configuration?
@hafesi The problem is that k10 couldn't connect to your kopia backup stored in the S3 bucket. It showed a "Failed to connect to the backup repository" message and an "Access Denied" error.To understand this better, checking the logs of the executor pods might help. Also, can you share the permissions you set for your S3 bucket?Ahmed Hagag
@asharma15 I understand that there's an existing open case that my colleague is managing. Upon reviewing the logs provided within that case, I've noticed some errors related to infrastructure profile validation:"cause\":{\"message\":\"Failed to get list of regions for Azure Service returned an error. Status=404 Code=\\\"SubscriptionNotFound\\\" Message=\\\"The subscription '14b81536-xxx-xxx-xxxx-xxxxxx' could not be found.\\\"\"}}}} It appears that there might be an issue with your Azure subscription. Could you verify that your subscription is active and valid, as indicated in the error message?Ahmed Hagag
@siva Kasten k10 is a data management platform for Kubernetes/Openshift applications. It provides a comprehensive set of features for backing up, restoring, and protecting Kubernetes data.in case you have Kubernetes/openshift cluster on your IBM Power Systems, then you need to visit our k10 docs page in order to check the prerequisites and storage compatibility.https://docs.kasten.io/latest/install/index.htmlhttps://docs.kasten.io/latest/install/storage.html
@tanveer.alamWhile exporting, K10 generates a snapshot within the kasten-io namespace. It then attempts to create a volume from these snapshots to be mounted into the copy-vol-data pod for data export.It appears that there may be certain restrictions on the Ceph side when it comes to creating volumes from snapshots. Unfortunately, the information you've supplied is insufficient to identify the problem. can you review the logs of the CSI provisioner and determine if any errors are present you also can attempt to manually create a snapshot from a volume, followed by the creation of a new volume from that snapshot, to see if this process can be successfully accomplished. you can also open a case with us through `my.veeam.com` and use `Kasten by veeam K10 Trial` in products while opening a case. Please collect the debug logs (https://docs.kasten.io/latest/operating/support.html#gathering-debugging-information) and upload the same to the case. We will get in touch and take a deep look at wh
@pascal.longuepee I think you still need to create rolebinding in kasten-io ns,The k10-ns-admin Role is added for secrets, configmaps access in the K10 release namespace. kubectl create rolebinding -n kasten-io test-k10-admin --role k10-ns-admin --serviceaccount kasten-io:k10-admin
@krn-alraedah can you start the backup again and at the same time run the below command and share it’s outputwhile true; do kubectl logs -l createdBy=kanister -n <APP_NAMESpaCE> -f ; sleep 2 ; done
@bryan.audo-ext I notice that you're employing PGOBackup is that correct ?k10 is generating a blueprint for this backup type within the kasten-io namespace. and you might need to modify the image repository and tag within the blueprint.Could you please provide a list of blueprints within the kasten-io namespace? You can achieve this by using either of the following commands:kubectl get blueprints -n kasten-ioorkubectl get blueprints.cr.kanister.io -n kasten-io
@bryan.audo-ext By default, the k10tools command will use the publicly available kanister-tools image at ghcr.io/kanisterio/kanister-tools:<Kanister version>. Since this image is not available in air-gapped environments, to override the default image, set the KANISTER_TOOLS environment variable to the kanister-tools image that is available in the air-gapped environment's local registry. The kanister-tools version can be found by running this command in a shell that has access to the public internet and with the appropriate K10 version. docker run --rm -it gcr.io/kasten-images/k10offline:<K10 version> list-images | grep kanister-tools.Example:export KANISTER_TOOLS=<your local registry>/<your local repository name>/kanister-tools:k10-<Kanister version>
@abhilashhm15 From what I understand, you want to take daily snapshots and retain them for 30/31 days. You also want to retain one snapshot from each of the previous 12 months.If I understand correctly then, Create a Kasten policy with the following settings: Frequency: DailyRetention:Hourly: 0Daily: 30Weekly: 0Monthly: 12Yearly: 0The daily retention setting will ensure that you always have 30 days of daily snapshots available by the end of each month. The yearly retention setting will ensure that you always have one snapshot from each of the previous 12 months available.Consider that maintaining 30 local snapshots at the end of each month results in additional storage expenses. and it's recommended to reduce local retention, which can be more expensive, and increase remote retention ( s3, NFS, etc.), which is typically more cost-effective
@abhilashhm15 The retention settings you've shared instruct K10 to maintain 31 snapshots per day. This implies that the retention policy would need to be run 31 times daily. If not, K10 will refrain from deleting any daily snapshots until it accumulates 31 of them. Consequently, K10 will retain snapshots until it reaches this count. When a new snapshot is taken, the oldest one is removed to ensure that there are always 31 snapshots in total.By following this approach, k10 will ensure that there are only 10 snapshots remaining at the end of each week.The same idea applies to monthly and yearly snapshots. You will have 12 snapshots per month and 7 snapshots per year.To ensure that your retention policy aligns precisely with your requirements, it would be helpful if you could provide specific details about the number of snapshots you wish to retain for each day, month, week, and year. Once you have clarified this, I can provide you with the proper settings.
Hello @fagner silva I noticed that the Kopia client pod named "copy-vol-data" remained in a pending state for 15 minutes, eventually causing the job to time out.To investigate further, please attempt to re-run the job, and then provide a description of the "copy-vol-data" pod using the following command: kubectl describe pod copy-vol-data-xxx -n kasten-ioThis will help us understand why the pod was stuck in the pending state, and you can also share the output with us for analysis.
@tg-test100 You have the option to set up an HTTPS listener for your Load Balancer; however, it's crucial to verify its compatibility with this feature.Alternatively, you can establish an Ingress with TLS Termination by generating a TLS-Typed Secret within the kasten-io namespace.
@Shubhadip Pal It would be greatly appreciated if you could share the solution to the problem as a point of reference for the community.
@It-Prooffice What version of k10 do you have?This issue was fixed starting from k10 V6.0.0https://docs.kasten.io/latest/releasenotes.html#relnotes-6-0-0
@Shubhadip Pal can you share the YAMLof rolebinding/clusterrolebing assigned to this user/group?
@Shubhadip Pal It appears RBAC issue to me, which role/cluster role is assigned to this user? I think you need to assign the user to the k10-mc-admin ClusterRole.
@jdiaz220481 It looks like the deployment config is not running successfully.Check the replication controller using the oc get rc command and ensure it is running or available.Check for error messages associated with the DeploymentConfig using oc describe dc <deploymentconfig-name>.
Hello @jdiaz220481 I am not an expert with ODF, but as far as I know, the Monitor, Pool, User, and Keyring values that are requested in the documentation are the configuration parameters for the Ceph RBD storage backend.These parameters are not exposed in the ODF UI, so you will need to get them from the Ceph configuration files.Keep in mind that. K10 supports Ceph RBD and Ceph FS snapshots and backups via their CSI drivers.
Hello @tamama3 Please ensure that you have successfully enabled the K10 multi-cluster manager. in order to check that Kindly provide the output of the following commands.kubectl get ns kasten-io-mc kubectl get cluster -n kasten-io-mAdditionally, you can attempt to access your multi-cluster dashboard by using the URL provided below:https://<ingress_FQDN>/k10/#/clustersRegards,Ahmed Hagag
Already have an account? Login
Enter your username or 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.
