Google Backup for GKE
Backup for GKE is a managed Kubernetes workload backup and restore service for GKE clusters (Google OAuth2).
OCNORA ships 11 typed Google Backup for GKE operations. Each node has a schema-driven form, input and output tables beside its settings, and is pre-flighted by Workflow Health before your first real run.
Before you connect Google Backup for GKE
- Authentication
- OAuth 2.0
- Credential
- {"client_id", "client_secret", "refresh_token"}
- Connection test
- Available: the stored credential can be checked against the provider when you add it. This is not a record that a test was run or passed.
What you can do with Google Backup for GKE
Operations, grouped by what they do to your data.
Create and send 2
Delete and cancel 2
A sample Google Backup for GKE workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no Google Backup for GKE trigger is needed.
- 2Get Backup Plangke_backup.get_backup_planRetrieve the details of a single BackupPlan.
- 3Create Backup Plangke_backup.create_backup_planCreates a new BackupPlan in a given location.
An outline built from this provider’s node contracts, not a recorded run. Each step’s output fields are available to the next in the field picker.
Every node below has a reference page: what it does, the connection it needs, its config fields with types, constraints and examples, and the shapes it emits.
Operations 11
- Create Backup PlanCreates a new BackupPlan in a given location.gke_backup.create_backup_plan
- Create Restore PlanCreates a new RestorePlan in a given location.gke_backup.create_restore_plan
- Delete Backup PlanDeletes an existing BackupPlan.gke_backup.delete_backup_plan
- Delete Restore PlanDeletes an existing RestorePlan.gke_backup.delete_restore_plan
- Get Backup PlanRetrieve the details of a single BackupPlan.gke_backup.get_backup_plan
- Get Restore PlanRetrieve the details of a single RestorePlan.gke_backup.get_restore_plan
- Get TagsReturns tags directly bound to a GCP resource.gke_backup.get_tags
- List Backup PlansLists BackupPlans in a given location.gke_backup.list_backup_plans
- List Restore PlansLists RestorePlans in a given location.gke_backup.list_restore_plans
- Update Backup PlanUpdate a BackupPlan.gke_backup.update_backup_plan
- Update Restore PlanUpdate a RestorePlan.gke_backup.update_restore_plan
Google Backup for GKE questions
- How does OCNORA authenticate with Google Backup for GKE?
- With a stored OAuth 2.0 credential, shaped {"client_id", "client_secret", "refresh_token"}. A connection test can check it when you add it.
- What can I automate with Google Backup for GKE?
- 11 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the Google Backup for GKE operation I need is not listed?
- Where Google Backup for GKE has an HTTP API, call it from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.
- Are there templates that use Google Backup for GKE?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are Google Backup for GKE calls controlled?
- Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.
See your first Google Backup for GKE workflow run.
Book a technical demo. We add the connection, pick a template or describe the workflow to Build with AI, and Workflow Health checks it before it runs.