How does Zeet handle multi-cloud deployments and ensure consistency across different cloud providers?
Zeet allows users to select multiple Kubernetes clusters across different cloud providers as deployment targets. Any changes made to an application are replicated across all selected clusters, ensuring centralized operations and consistent application behavior regardless of the underlying cloud infrastructure. This enables seamless deployment and management across up to 7 public clouds.
Can Zeet integrate with our existing version control system and how does it manage CI/CD workflows?
Yes, Zeet integrates directly with popular Version Control Systems (VCS) including GitHub, GitLab, and Bitbucket. It provides robust built-in CI/CD capabilities with features like auto-deploys, manual deploy approvals, branch resource configuration, and rolling deploys. It also handles automatic rollbacks in the event of a bad deployment, ensuring stability.
What types of infrastructure can be provisioned using Zeet's blueprints, and can we create our own custom blueprints?
Zeet's blueprints are pre-packaged design patterns for common cloud-native use cases, such as self-hosting databases, setting up serverless functions, or provisioning general infrastructure. Users can also create custom blueprints by bringing their own Infrastructure as Code (IaC) packages, like Kubernetes Manifests or Helm Charts, allowing for customized input variables and configurations that can be shared across the team.
How does Zeet provide observability and monitoring for deployed applications and infrastructure?
Zeet offers built-in observability features including metrics, logging, and a centralized dashboard. It automatically integrates monitoring stacks like Prometheus and Grafana into Kubernetes clusters and applications. Additionally, it provides a Status Page for a high-level overview of clouds, clusters, and projects, along with notifications for deploy, build, and Kubernetes Pod crashes, which can be sent to integrations like Slack and Discord.
Is it possible to manage Terraform remote state directly within Zeet, and how does that process work?
Yes, Zeet can manage Terraform remote state. When deploying a Terraform Stack, Zeet will automatically provision a cloud bucket (either AWS or GCP) and maintain the Terraform state within that bucket. This streamlines the management of infrastructure as code by centralizing state management.
What kind of self-service capabilities does Zeet offer to developers, and how does it balance this with operational control?
Zeet empowers developers with self-service capabilities through its Project Creation flow and centralized dashboard, allowing them to provision, observe, and manage resources. This includes viewing logs and metrics, configuring auto-scaling, and managing releases. Operational control is maintained through features like manual deploy approvals, audit logs, and the ability to define infrastructure blueprints, ensuring that deployments adhere to best practices and policies set by SRE/DevOps teams.