Can HumDay connect to Google Backup for GKE?

Yes. HumDay reads Google Backup for GKE's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 20 operations are documented.

Do I need to write code to automate Google Backup for GKE?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your Google Backup for GKE account.

What can HumDay do in Google Backup for GKE?

10 of the 20 documented operations change something in Google Backup for GKE, and 10 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my Google Backup for GKE account safe?

Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to Google Backup for GKE is held behind that approval.

Automate Google Backup for GKE

HumDay reads Google Backup for GKE’s own published API description and derives 20 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.

What Google Backup for GKE is

Backup for GKE is a managed Kubernetes workload backup and restore service for GKE clusters.

API host: gkebackup.googleapis.com

What HumDay can do in Google Backup for GKE

10 documented operations change something in Google Backup for GKE.

POSTCreates a new Restore for the given RestorePlan./v1/{parent}/restores
POSTCreates a new BackupPlan in a given location./v1/{parent}/backupPlans
POSTCreates a new RestorePlan in a given location./v1/{parent}/restorePlans
POSTCreates a Backup for the given BackupPlan./v1/{parent}/backups
DELETEDeletes an existing Restore./v1/{name}
PATCHUpdate a Restore./v1/{name}
POSTStarts asynchronous cancellation on a long-running operation./v1/{name}:cancel
POSTSets the access control policy on the specified resource./v1/{resource}:setIamPolicy
POSTReturns permissions that a caller has on the specified resource./v1/{resource}:testIamPermissions
DELETEDeletes a long-running operation./v1/{name}/operations

What HumDay can read from Google Backup for GKE

These are the operations a schedule or a trigger can watch.

GETRetrieve the details of a single VolumeRestore./v1/{name}
GETGets the access control policy for a resource./v1/{resource}:getIamPolicy
GETLists information about the supported locations for this service./v1/{name}/locations
GETLists the Backups for a given BackupPlan./v1/{parent}/backups
GETLists operations that match the specified filter in the request./v1/{name}/operations
GETLists the Restores for a given RestorePlan./v1/{parent}/restores
GETLists BackupPlans in a given location./v1/{parent}/backupPlans
GETLists RestorePlans in a given location./v1/{parent}/restorePlans
GETLists the VolumeBackups for a given Backup./v1/{parent}/volumeBackups
GETLists the VolumeRestores for a given Restore./v1/{parent}/volumeRestores

How automating Google Backup for GKE works

Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
See it proven. The program runs and shows you the result before it is allowed near your live Google Backup for GKE account.
Grant access, then go live. You approve the specific Google Backup for GKE operations it may use — and only those.