Google Cloud Platform Kubernetes Engine (GKE)
Connect your account from Google Cloud Platform Kubernetes Engine (GKE) and Wodby will spin up a ready-to-run Kubernetes cluster for you. We will install all necessary infrastructure, so you can deploy your app using one of our stacks in a few clicks.
Specific to this provider
What Wodby sets up on Google Kubernetes Engine
Wodby creates a Google Kubernetes Engine cluster in the Google Cloud project you select. Sign in with OAuth, or upload the key of a service account that you created with the roles Wodby needs.
Zonal or highly available
A GKE cluster can be created as highly available across several zones or in a single zone, so the choice between resilience and a smaller footprint is yours.
A separate project keeps costs visible
Wodby recommends a dedicated Google Cloud project for the resources it creates, which makes cloud costs easier to follow. Those resources also share a common Wodby name prefix.
Standard clusters only
Serverless GKE clusters are not supported at present. Wodby creates and manages all of the cluster's resources through Deployment Manager.
Persistent disks for volumes
Volumes are Compute Engine Persistent Disks, with one new disk for each persistent volume claim. The size of the node disk is chosen when the cluster is created.
Cloud SQL beside the cluster
A Cloud SQL database can be placed with a GKE cluster that was created under the same integration. Wodby supports MySQL and PostgreSQL there, zonal or regional.
Read the Google Cloud guide for requirements, setup steps, and limits.
Infrastructure we install and maintain
A cluster ready to run your apps
Wodby installs and connects the services for app traffic, resource monitoring, and provider integrations. Start deploying with these essentials in place, and keep them and the Kubernetes version current with Wodby.
Application routing
Publish HTTP and HTTPS endpoints for your apps. Wodby configures the gateway and routes requests to the appropriate service.
- Envoy Gateway
Know how your cluster is performing
View CPU, memory, and storage metrics in Wodby to understand resource usage and investigate capacity issues without assembling your own monitoring stack.
- Monitoring
- Node exporter
- Kubernetes state metrics
Keep your cluster current with less manual work
Wodby upgrades its infrastructure and the infrastructure app stacks automatically, and can upgrade the Kubernetes version too, each with its own version policy and maintenance window. You choose what may change and when, and every upgrade is a task you can follow.
Automatic infrastructure upgrades
Keep Wodby's cluster networking and routing setup current. Enable automatic upgrades and choose which patch, minor, and major changes your cluster may receive.
Automatic infrastructure app updates
Update gateway, monitoring, and controller stacks automatically with their own version policy, including newer revisions of the same version.
Automatic Kubernetes upgrades
Turn automatic upgrades on and Wodby moves GKE Standard clusters to new Kubernetes patch releases in your maintenance window, while the provider keeps its system components current. They are off by default, because each upgrade replaces the nodes and restarts every pod. You can also review the upgrade plan and start one yourself.
Maintenance on your schedule
Set separate weekdays, hours, and time zones for automatic infrastructure, infrastructure app, and Kubernetes upgrades, so routine maintenance starts when it suits your team.
Reviewable, traceable updates
Review infrastructure app changelogs, Kubernetes upgrade plans, and available release notes. Follow upgrade tasks, retry failed operations, and receive success or failure emails for automatic infrastructure and Kubernetes upgrades.
App environment network isolation
On supported clusters, network policies isolate incoming traffic between app environments while keeping services in the same environment connected.
Need more capacity? On supported scalable managed clusters, set minimum and maximum node counts and let the provider's autoscaler adjust capacity to workload demand. Explore cluster scaling →
How cluster updates work →Budget self-hosted Kubernetes on your own servers
Google Cloud Platform offers VMs that can be used for a self-hosted Kubernetes setup, which means you can connect a VM, add more VMs as worker nodes later, and avoid the extra managed Kubernetes overhead around the control plane, cloud load balancer, and block storage. The tradeoff is no autoscaling and no high availability compared to a managed cluster, but it can be a good fit for smaller workloads and lower budgets. Read more on the self-hosted Kubernetes page.
Popular stacks
Browse common Wodby stacks and open the stack page for setup, services, integrations, and deployment options.
Prefer not to use your own cloud account or server?
If you want the Wodby Kubernetes workflow without a provider account or server of your own, deploy with Wodby Cloud. It gives you the same managed stacks and deployment model without requiring a cluster in your own cloud account or on your own server.
No separate provider account
Start deploying without creating and wiring AWS, GCP, Azure, DigitalOcean, or dedicated server infrastructure first.
Less infrastructure hassle
Wodby provides the cluster and platform foundation so your team can focus on applications instead of setting up and owning the infrastructure itself.
Simple pay-as-you-go model
Wodby Cloud pricing provides a simpler way to get started with a managed Kubernetes environment and predictable platform costs.
Deploy on Google Cloud Platform Kubernetes Engine (GKE) with Wodby
Launch a production-ready environment faster with Wodby-managed infrastructure, deployment workflows, and application stacks.