• EN

Replies posted by jaiganeshjk

240 Comments

zimbres
zimbresNew Here
asked in Kasten K10 Support

Snapshot restore to same NS on OpenEBS cStor

@zimbres Thank you for posting your question here.During restore of an Application, K10 always deletes the PVC of the application and recreates it with the snapshot.If the snapshot of your PVC is tied to the lifecycle of the volume, then you will see problems with restore as the snapshot would eventually be destroyed when the PVCs are deleted for restore.In this case, it would be better to have your application exported to an external Target and use it to do an in-place restore.Please let me know if you have more questions.

2
jaiganeshjk
1 year ago
N
ntiwari38Comes here often
asked in Kasten K10 Support

catalog-svc-5c6ffff9f9-lbgvl pod is going on Init:CrashLoopBackOff mode.

@ntiwari38 Init crashlooping of Catalog SVC mostly occurs when it cannot write data into its Persistent Volume.If you are using an NFS StorageClass which doesn’t support fsGroup fields in the workload securityContext, You might have to manually change the permissions & ownership for the directory to the user which catalog uses(UID/GID is 1000) You can look at the reason for crashlooping with the below commandkubectl logs deploy/catalog-svc --all-containers -n kasten-io 

2
jaiganeshjk
1 year ago
G
Garland7362New Here
asked in Kasten K10 Support

K10 not working with Linkerd service mesh

@Garland7362 Glad that the workaround works for you now.I don’t have any timelines. It has to go through the PM review and it will be worked upon.All I can say that the bug will be fixed before the enhancement. IMO, your workaround to add annotations to the kanister pod  will ensure your exports work until we have the enhancement in this workflow, unless something changes in the linkerd wrt to the annotation.

18
FRubens
2 months ago
G
Garland7362New Here
asked in Kasten K10 Support

K10 not working with Linkerd service mesh

I think I know the answer. It seems to be a bug from our side(I will file a bug and get it fixed).The keyReference(from the configMap) that is added to the workloads is kanisterPodCustomAnnotationsWhere as the Key that was added in the configmap is KanisterPodCustomAnnotationsNotice the upper case K in the configMap and lowercase in the deployments.You might have to workaround it for the time-being by editing the configmap and changing the key to kanisterPodCustomAnnotations (with lowercase k) 

18
FRubens
2 months ago
G
Garland7362New Here
asked in Kasten K10 Support

K10 not working with Linkerd service mesh

@Garland7362I can confirm that the linkerd proxy container is where the commands are being run.We seem to be running  exec commands in first container as we don't expect to have multiple containers with the pod that we dynamically spin-up.We will have to enhance this behaviour for your use case. I have filed an enhancement request to support this configuration. I went through the Linkerd issues to find out the reason for adding the proxy container as the first container.They mention that this change was purposefully added to avoid startup issues in this github issue .It seems that you can use annotation in the workload config.linkerd.io/proxy-await: "disabled"  to disable this feature.Thinking about working around this, You could try using custom kanister annotations helm value to add this annotation to the pods spinned up by K10.This would make sure that the kanister-tools container be the first container and should resolve your issue for time-being.https://docs.kasten.io/latest/kanis

18
FRubens
2 months ago
L
lidwComes here often
asked in Kasten K10 Support

kasten k10 nfs sidecat backup failed

@lidw Thanks for posting your question.From your message and the topic, I assume that you are trying to export your application by injecting Sidecar(Generic Volume snapshot) to an NFS target. Is that right ?Error message says that it is failing to create a repository in the target location. It could be a permission issue if it is an NFS target location profile.You could take a look at the executor pod logs to find out the reason for the failure of the repository create command. 

3
L
1 year ago
G
Garland7362New Here
asked in Kasten K10 Support

K10 not working with Linkerd service mesh

I see that you have a support case with us as well. Let me confirm if that is the cause of the issue and see what could be done if this is the case.

18
FRubens
2 months ago
G
Garland7362New Here
asked in Kasten K10 Support

K10 not working with Linkerd service mesh

I am just checking how k10 runs exec command in the newly created pods. We could be trying to run k10 kopia commands in first container but for some reason it could be running in linkerD proxy container rather than the kanister-tools container 

18
FRubens
2 months ago
G
Garland7362New Here
asked in Kasten K10 Support

K10 not working with Linkerd service mesh

Hi @Garland7362 Thank you for posting the question.From the error message, it seems that the kopia binary is not available in the pod that is spinned-up for exports.It could be either create-repo or copy-vol-data pod. Do you see which image it is trying to use ? 

18
FRubens
2 months ago
P
pascalzeroNew Here
asked in Kasten K10 Support

Will Kasten use Shallow Read-Only CephFS snapshots?

Thank you for your interest. We are tracking this internally.However, we don’t have any timelines yet.@pascalzero  You are right. As I mentioned earlier, We reuse the accessMode of the PVC from the original PVC that is being exported.We would update you once we have the ability in the product. 

20
jaiganeshjk
2 months ago
N
ntiwari38Comes here often
asked in Kasten K10 Support

Not able to create snapshot all pod are running.

Hi Neha,For immediate assistance, I would suggest you to open a case with us by logging into my.veeam.com and selecting the product Veeam Kasten by K10 Trial.You can upload the entire log bundle to the case.  

15
jaiganeshjk
1 year ago
N
ntiwari38Comes here often
asked in Kasten K10 Support

Not able to create snapshot all pod are running.

@ntiwari38 In addition to what Satish had asked, Can you confirm if the useraccount that you are using to access K10 UI, is a K10-admin/Cluster-admin user ?Or is it just a namespace admin or a basic user with access to few namespace ?The RunOnce action is an admin action and can only be done by a user with cluster-admin privilege or at-least with the privilege to create runaction resource(which is a cluster-scoped resource at the moment)

15
jaiganeshjk
1 year ago
R
rust84Not a newbie anymore
asked in Kasten K10 Support

Key collision errors after K10 cluster restore

@rust84 I am not exactly sure on this error, However from the message, it suggests that there is an artifact in the catalog that has the same key/value as the resource that you are trying to backup. There are few logs and outputs which we would like to look at and it could be better handled and tracked through a case(As this might involve looking through the saved artifacts from your namespace). Would you be able to open a case with us from my.veeam.com and select Veeam Kasten by K10 Trial under the product to raise a case with the debug logs?

5
jaiganeshjk
1 year ago
L
lidwComes here often
asked in Kasten K10 Support

kasten k10 nodeport mode environment using keycloak authorization resetting login error

 @lidw Thanks for confirming that it worked.Would you be able to mark the comment as answer ?

3
jaiganeshjk
1 year ago
R
Refresh2260New Here
asked in Kasten K10 Support

Kasten does not recognize Openstack Storage Driver Settings.

@Refresh2260 Thank you for posting your question here.Openstack infrastructure profile is supported only for PVCs provisioned with Cinder In-Tree provisioner(kubernetes.io/cinder). Most of the times, we use infrastructure profiles only in cases where the provisoner doesn’t support taking snapshots the CSI way(Except for Vsphere).Since Cinder CSI driver already supports snapshotting through volumeSnapshot resources, I would suggest you to make use of that by creating volumesnapshotclass and annotating it with the above annotation.https://docs.kasten.io/latest/install/storage.html#csi-snapshot-configuration

2
jaiganeshjk
1 year ago
T
thatmanNot a newbie anymore
asked in Kasten K10 Support

After successful "Create policy" and delete policy, "Create policy" now dimmed

Just an FYI, It could be useful for someone who comes across this post at a later point. If you think some external gitops controller could be responsible for the deletion of this configMap because of the declarative state, You could use the below helm values to set the EULA info declaratively. eula.accept Whether to enable accept EULA before installation false eula.company Company name. Required field if EULA is accepted None eula.email Contact email. Required field if EULA is accepted None

5
T
1 year ago
T
thatmanNot a newbie anymore
asked in Kasten K10 Support

After successful "Create policy" and delete policy, "Create policy" now dimmed

@thatman Thanks for your detailed explanation with the timelines.I think I may know what happened with you. When you install K10 for the first time, you get a pop-up to accept EULA with your email and company name.This is stored as a configMap named k10-eula-info in K10 namespace.Without accepting the EULA, most of the actions in UI will be disabled.Since you mentioned you accepted that earlier, I am assuming this ConfigMap is somehow deleted from your kasten-io namespace, forcing you to accept it again.Since you accepted the second time, it might have started working for you again.

5
T
1 year ago
T
thatmanNot a newbie anymore
asked in Kasten K10 Support

After successful "Create policy" and delete policy, "Create policy" now dimmed

@thatman Thank you for posting your question.Does the useraccount you use to login to the UI, have permissions to create profile in kasten-io namespace ?kubectl auth can-i create policies.config.kio.kasten.io -n kasten-io --as=<username>#if you are using serviceAccount token, then use the below commandkubectl auth can-i create policies.config.kio.kasten.io -n mysql --as=system:serviceaccount:<namespaceName:serviceaccountName> 

5
T
1 year ago
L
lidwComes here often
asked in Kasten K10 Support

kasten k10 nodeport mode environment using keycloak authorization resetting login error

@lidw Thanks for posting your question.The redirect URL should be the URL pointing to gateway svc which should have your NodePort in it.Would you please update your redirectURL value to include the nodePort as well. Your command should look like this.helm upgrade k10 k10-5.5.4.tgz --namespace=kasten-io -f k10_val.yaml \  --set auth.oidcAuth.enabled=true \  --set auth.oidcAuth.providerURL="http://192.168.40.10:8080/realms/kasten" \  --set auth.oidcAuth.redirectURL="http://192.168.40.11:32051" \  --set auth.oidcAuth.scopes="groups profile email" \  --set auth.oidcAuth.usernameClaim="email" \  --set auth.oidcAuth.groupClaim="groups" \  --set auth.oidcAuth.prompt="login" \  --set auth.oidcAuth.clientID="kasten" \  --set auth.oidcAuth.clientSecret="RbyRI3FgBrmuqNM2NhEQ7lMNzWp1663L" 

3
jaiganeshjk
1 year ago
N
ntiwari38Comes here often
asked in Kasten K10 Support

catalog-svc pod is not running.

@ntiwari38 Thanks for confirming. Glad that it worked for you.Would you be able to mark the comment as answer ?

5
A
1 year ago
N
ntiwari38Comes here often
asked in Kasten K10 Support

catalog-svc pod is not running.

@ntiwari38 Thank you for posting the question.From the events, I could see that the kanister-sidecar container from the catalog-svc is failing as it couldn’t pull the image from ghcr.io.Can you confirm if your environment allows pulling images from github container registry (ghcrio) ? If yes, it could be transient problem, You can try recreating the pod.You can also try to confirm if the image is accessible from you environment by running another pod with that image.kubectl run kanister-tools --rm -it --image ghcr.io/kanisterio/kanister-tools:0.85.0 -n kasten-io -- bash BTW, I can confirm that this image is available and accessible without any problem❯ docker pull ghcr.io/kanisterio/kanister-tools:0.85.00.85.0: Pulling from kanisterio/kanister-tools1d6f30850896: Pull complete 97d7b37e7232: Pull complete 196b571ab112: Pull complete 74d0dc5eeb47: Pull complete 187f5a0f24c6: Pull complete 701b65989276: Pull complete Digest: sha256:0c8da74a06fcfba32c7c278861b1e7e29b40e40f2a5e38c195f4339b81

5
A
1 year ago
B
brian96New Here
asked in Kasten K10 Support

Failed to snapshot volumes (vSphere CSI with RKE2)

I found it is the RWX volume is causing the issue. So, I believe Kasten K10 does not support volume backed by vSphere CNS which mounted as NFS from VSAN File Service. Is that right?     @brian96 Thank you for posting your question.I suppose you are right with the support for VSAN file service. We haven’t tested this.Let me confirm if that is the case and update you.

4
jaiganeshjk
1 year ago
tinto.1970
tinto.1970Comes here often
asked in Kasten K10 Support

import policies on "dr" site fail and go to "failed" state

Even this is a weird behaviour for ArgoCD as we had earlier tested with the same and we did not come across this issue.We did not support policies being created with gitops until 5.5 major release of k10. So we started supporting it very recently. Can you confirm if you are using any specific sync-options with ArgoCD ?I can test it for you from my side as well. 

4
jaiganeshjk
1 year ago
F
flavio_bitstanComes here often
asked in Kasten K10 Support

Kanister Blueprint for MySQL fails

Yes the example is designed for standalone mysql and not mysql replicated cluster.That is just an example for the end users to understand the functionality and you can customise it based on your requirements.In this case, It can be fixed easily.All you need is to change the hostname in the dump and restore commands that has the hostname configured.Currently it is pointing to this label value {{ index .Object.metadata.labels "app.kubernetes.io/instance" }} from the workload to get the service name.Value of this label is `mysql` and hence the template is rendered and the dump command uses mysql as hostname.You can actually edit the blueprint to add some other template which might render into `mysql-primary` or hardcode the hostname in the blueprint.You will have to change templates after `-h` in the below places.https://github.com/kanisterio/kanister/blob/master/examples/mysql/blueprint-v2/mysql-blueprint.yaml#L34https://github.com/kanisterio/kanister/blob/master/examples/mysql/blueprint

10
jaiganeshjk
8 months ago
S
stefanodemartiniNot a newbie anymore
asked in Kasten K10 Support

Problem installing k10 - helm

@stefanodemartini Thanks for posting the question here.From the above error messages, I understand that there is a problem with the permissions of the PVCs.All the pods which use PVCs are failing to start/initialise and the error message that I see in the logs are permission denied(except Grafana, which uses initContainer to change permissions of the directory).There is something wrong with the directory permissions and ownership for those PVCs. Let me take a look at the CephFS if it has any limitations wrt fsGroup settings in the workload.

3
S
1 year ago

Badge winners

Show all badges
Terms & Conditions