Kamforka

Is this feature implemented yet, or still under development?

It's definitely a bug, if I change the endpoint url from `https://` to `http://` and also change the proxy scheme to `http://` it works, otherwise it fails.

Hi @Lyndon-Li! So technically the status of the restore is `PartiallyFailed` however when I do a simple describe I see the below in the warning/error section: ```bash Warnings: Velero: Cluster:...

Okay I've checked the node agents, and indeed I could observer OOM killed statuses. I've increased the memory limit to a much higher value and rerunning the restore, will let...

After increasing the resource limits the node-agent was not killed due to OOM but the restore failed again. I checked the logs and I could only see these lines: ```bash...

By digging deeper in the related DataDownload resource: ```bash $ k describe datadownloads.velero.io my-backup-20240307151012-cl925 Name: my-backup-20240307151012-cl925 Namespace: velero Labels: velero.io/accepted-by=d6c37003-a9f8-45db-ba7e-e965bd8136d8 velero.io/async-operation-id=dd-36e7ca5e-3ff9-48f8-ac4c-42483370ec30.cdcd4260-b15a-4148daa0e velero.io/restore-name=my-backup-20240307151012 velero.io/restore-uid=36e7ca5e-3ff9-48f8-ac4c-42483370ec30 Annotations: API Version: velero.io/v2alpha1 Kind: DataDownload Metadata:...

Okay I checked the node-agents again and seems like they get evicted one by one and then recreated. So I checked the status of the evicted ones: ```bash Status: Failed...

Alright so the root cause was that the node of the node-agent was running out of temporary storage, which is weird as I wouldn't expect 50 GB to be insufficient...

Hi everyone, Thanks for the information. Sorry for not following up on them immediately but I was doing a couple of test restores today and I still think something is...

We are closing this issue as it pertains to the 1.x version of thehive4py, which is no longer supported. We recommend upgrading to the latest release for continued support or...