Can HumDay connect to Google Kubernetes Engine?

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

Do I need to write code to automate Google Kubernetes Engine?

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 Kubernetes Engine account.

What can HumDay do in Google Kubernetes Engine?

45 of the 61 documented operations change something in Google Kubernetes Engine, and 16 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my Google Kubernetes Engine 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 Kubernetes Engine is held behind that approval.

Automate Google Kubernetes Engine

HumDay reads Google Kubernetes Engine’s own published API description and derives 61 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 Kubernetes Engine is

Builds and manages container-based applications, powered by the open source Kubernetes technology.

API host: container.googleapis.com

What HumDay can do in Google Kubernetes Engine

45 documented operations change something in Google Kubernetes Engine.

POSTCreates a cluster, consisting of the specified number and type of Google Compute Engine instances./v1beta1/{parent}/clusters
POSTCreates a node pool for a cluster./v1beta1/{parent}/nodePools
DELETEDeletes a node pool from a cluster./v1beta1/{name}
PUTUpdates the version and/or image type of a specific node pool./v1beta1/{name}
POSTCancels the specified operation./v1beta1/{name}:cancel
POSTSetNodePoolSizeRequest sets the size of a node pool./v1beta1/{name}:setSize
POSTRolls back a previously Aborted or Failed NodePool upgrade./v1beta1/{name}:rollback
POSTSets the addons for a specific cluster./v1beta1/{name}:setAddons
POSTSets the logging service for a specific cluster./v1beta1/{name}:setLogging
POSTSets the locations for a specific cluster./v1beta1/{name}:setLocations
POSTUpdates the master for a specific cluster./v1beta1/{name}:updateMaster
POSTEnables or disables the ABAC authorization mechanism on a cluster./v1beta1/{name}:setLegacyAbac
POSTSets the NodeManagement options for a node pool./v1beta1/{name}:setManagement
POSTSets master auth materials./v1beta1/{name}:setMasterAuth
POSTSets the monitoring service for a specific cluster./v1beta1/{name}:setMonitoring
POSTSets the autoscaling settings of a specific node pool./v1beta1/{name}:setAutoscaling
POSTCompleteNodePoolUpgrade will signal an on-going node pool upgrade to complete./v1beta1/{name}:completeUpgrade
POSTStarts master IP rotation./v1beta1/{name}:startIpRotation
POSTEnables or disables Network Policy for a cluster./v1beta1/{name}:setNetworkPolicy
POSTSets labels on a cluster./v1beta1/{name}:setResourceLabels
POSTCompletes master IP rotation./v1beta1/{name}:completeIpRotation
POSTSets the maintenance policy for a cluster./v1beta1/{name}:setMaintenancePolicy
POSTCreates a cluster, consisting of the specified number and type of Google Compute Engine instances./v1beta1/projects/{projectId}/zones/{zone}/clusters
POSTCreates a node pool for a cluster./v1beta1/projects/{projectId}/zones/{zone}/clusters/{clusterId}/nodePools
DELETEDeletes the cluster, including the Kubernetes endpoint and all worker nodes./v1beta1/projects/{projectId}/zones/{zone}/clusters/{clusterId}
PUTUpdates the settings for a specific cluster./v1beta1/projects/{projectId}/zones/{zone}/clusters/{clusterId}
POSTCancels the specified operation./v1beta1/projects/{projectId}/zones/{zone}/operations/{operationId}:cancel
POSTSets master auth materials./v1beta1/projects/{projectId}/zones/{zone}/clusters/{clusterId}:setMasterAuth
POSTStarts master IP rotation./v1beta1/projects/{projectId}/zones/{zone}/clusters/{clusterId}:startIpRotation
POSTEnables or disables Network Policy for a cluster./v1beta1/projects/{projectId}/zones/{zone}/clusters/{clusterId}:setNetworkPolicy
POSTCompletes master IP rotation./v1beta1/projects/{projectId}/zones/{zone}/clusters/{clusterId}:completeIpRotation
POSTSets the maintenance policy for a cluster./v1beta1/projects/{projectId}/zones/{zone}/clusters/{clusterId}:setMaintenancePolicy
POSTSets the addons for a specific cluster./v1beta1/projects/{projectId}/zones/{zone}/clusters/{clusterId}/addons
POSTUpdates the master for a specific cluster./v1beta1/projects/{projectId}/zones/{zone}/clusters/{clusterId}/master
POSTSets the logging service for a specific cluster./v1beta1/projects/{projectId}/zones/{zone}/clusters/{clusterId}/logging
POSTSets the locations for a specific cluster./v1beta1/projects/{projectId}/zones/{zone}/clusters/{clusterId}/locations
POSTEnables or disables the ABAC authorization mechanism on a cluster./v1beta1/projects/{projectId}/zones/{zone}/clusters/{clusterId}/legacyAbac
POSTSets the monitoring service for a specific cluster./v1beta1/projects/{projectId}/zones/{zone}/clusters/{clusterId}/monitoring
POSTSets labels on a cluster./v1beta1/projects/{projectId}/zones/{zone}/clusters/{clusterId}/resourceLabels
DELETEDeletes a node pool from a cluster./v1beta1/projects/{projectId}/zones/{zone}/clusters/{clusterId}/nodePools/{nodePoolId}
POSTRolls back a previously Aborted or Failed NodePool upgrade./v1beta1/projects/{projectId}/zones/{zone}/clusters/{clusterId}/nodePools/{nodePoolId}:rollback
POSTUpdates the version and/or image type of a specific node pool./v1beta1/projects/{projectId}/zones/{zone}/clusters/{clusterId}/nodePools/{nodePoolId}/update
POSTSetNodePoolSizeRequest sets the size of a node pool./v1beta1/projects/{projectId}/zones/{zone}/clusters/{clusterId}/nodePools/{nodePoolId}/setSize
POSTSets the autoscaling settings of a specific node pool./v1beta1/projects/{projectId}/zones/{zone}/clusters/{clusterId}/nodePools/{nodePoolId}/autoscaling
POSTSets the NodeManagement options for a node pool./v1beta1/projects/{projectId}/zones/{zone}/clusters/{clusterId}/nodePools/{nodePoolId}/setManagement

What HumDay can read from Google Kubernetes Engine

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

GETGets the specified operation./v1beta1/{name}
GETGets the OIDC discovery document for the cluster./v1beta1/{parent}/.well-known/openid-configuration
GETGets the public component of the cluster signing keys in JSON Web Key format./v1beta1/{parent}/jwks
GETLists all clusters owned by a project in either the specified zone or all zones./v1beta1/{parent}/clusters
GETFetches locations that offer Google Kubernetes Engine./v1beta1/{parent}/locations
GETLists the node pools for a cluster./v1beta1/{parent}/nodePools
GETReturns configuration info about the Google Kubernetes Engine service./v1beta1/{name}/serverConfig
GETLists all operations in a project in the specified zone or all zones./v1beta1/{parent}/operations
GETLists subnetworks that can be used for creating clusters in a project./v1beta1/{parent}/aggregated/usableSubnetworks
GETLists all clusters owned by a project in either the specified zone or all zones./v1beta1/projects/{projectId}/zones/{zone}/clusters
GETLists all operations in a project in the specified zone or all zones./v1beta1/projects/{projectId}/zones/{zone}/operations
GETReturns configuration info about the Google Kubernetes Engine service./v1beta1/projects/{projectId}/zones/{zone}/serverconfig
GETGets the details for a specific cluster./v1beta1/projects/{projectId}/zones/{zone}/clusters/{clusterId}
GETGets the specified operation./v1beta1/projects/{projectId}/zones/{zone}/operations/{operationId}
GETLists the node pools for a cluster./v1beta1/projects/{projectId}/zones/{zone}/clusters/{clusterId}/nodePools
GETRetrieves the requested node pool./v1beta1/projects/{projectId}/zones/{zone}/clusters/{clusterId}/nodePools/{nodePoolId}

How automating Google Kubernetes Engine 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 Kubernetes Engine account.
Grant access, then go live. You approve the specific Google Kubernetes Engine operations it may use — and only those.