DOCSEARCHbyAlgolia
Submit Docs

Opta Documentation

website·Indexed 32 days ago

https://docs.opta.dev/

Infrastructure management tool for deploying Kubernetes clusters and cloud resources across AWS, Azure, and GCP. Includes documentation for cloud-specific modules such as GKE, AKS, VPCs, databases (PostgreSQL, MySQL), Redis, and observability integrations like Datadog, as well as guides for security architecture and VPC peering.

Tokens
52.9K
Snippets
241
Records
440
Agent score
63%

What's inside Opta

  1. Overview of available Opta AzureRM modules

    Opta provides a variety of module types for use in AzureRM YAML configurations to manage infrastructure, Kubernetes clusters, and third-party integrations. Available modules include:

    • base: Sets up virtual networks, private subnets, security groups, default encryption key vaults, and container registries.
    • k8s-cluster: Creates an Azure Kubernetes Service (AKS) cluster and a default node pool.
    • k8s-base: Creates base infrastructure packaged into Opta environments.
    • k8s-service: Deploys a Kubernetes application.
    • k8s-manifest: Plugs a Kubernetes manifest into an Opta k8s cluster.
    • helm-chart: Plugs a custom Helm chart into an Opta k8s cluster.
    • postgres: Creates a PostgreSQL database.
    • datadog: Integrates Datadog for observability.
    • external-ssl-cert: Manages external SSL certificates.
    • external-state: Allows referencing external, pre-existing Terraform states within Opta.
    • custom-terraform: Allows the use of custom Terraform modules.

  2. Overview of available Opta modules for Google Cloud

    Opta provides a set of predefined module types that can be used in an Opta YAML configuration to provision Google Cloud Platform (GCP) infrastructure. These modules cover core networking, Kubernetes clusters, managed databases, and third-party integrations.

  3. Overview of the Opta IaC framework

    Opta is an infrastructure-as-code (IaC) framework that allows developers to define infrastructure using high-level constructs instead of low-level cloud configurations. Opta translates these constructs into Terraform configuration files, ensuring that users are not locked into the framework and can maintain or extend their infrastructure using standard Terraform code.

  4. Overview of the k8s-base infrastructure module

    The k8s-base module deploys the core infrastructure components required for Opta Kubernetes environments. It automatically packages and manages the following tools:

    • Autoscaler: Handles scaling of EC2 instances.
    • Ingress Nginx: Manages public exposure of services.
    • Metrics Server: Enables scaling of deployments based on CPU and memory usage.
    • Linkerd: Provides a service mesh for the environment.
    • Cert Manager: Manages internal SSL certificates.

  5. Overview of the k8s-base infrastructure module

    The k8s-base module deploys the core infrastructure required for Opta Kubernetes environments. It automatically packages and installs the following components:

    • Ingress Nginx: Used to expose services to the public internet.
    • Linkerd: A service mesh for observability, security, and reliability.
    • Cert Manager: Handles internal SSL certificate management.
    • Custom Load Balancer and DNS Routing: Specifically configured to support the Ingress Nginx installation.

  6. Supported deployment environments for Opta

    Opta supports deployments across the following environments: AWS, GCP, Azure public clouds, and local machine deployments.

  7. Understand Opta GCP network architecture

    Opta deployments on GCP are configured within a single region and subnet, distributed across availability zones. The subnet is private; only the load balancer and GCS buckets are reachable from the public internet. To ensure databases and caches remain private without public endpoints, Opta utilizes service networking peering (Private Service Connect).

  8. Understand Opta's Infrastructure-As-Code workflow

    Opta uses an Infrastructure-As-Code (IaC) model where users define their infrastructure via configuration files. The Opta CLI is then used to connect to a cloud account and provision resources to match that configuration. The CLI can be executed from a local development machine or integrated into CI/CD pipelines such as GitHub Actions or Jenkins.

  9. Configure the Opta base AWS infrastructure

    The aws-base module sets up the VPCs, a default KMS key (used for Redis, DocumentDB, EKS, etc.), and the database/cache subnets for the environment. For most users, the default settings are sufficient and no manual configuration of fields or outputs is required.

  11. Understand Opta's Kubernetes cluster architecture

    Opta's Kubernetes topology is organized into namespaces divided between third-party integrations and Opta services. All components are managed using Helm V3 and deployed into their own respective namespaces.

  12. Understand Opta AWS Network Architecture

    Opta AWS deployments are configured within a single region across three availability zones (AZs). The networking is split into public and private subnets: the public subnet is used exclusively for the public load balancer, while all EC2 instances (VMs) and databases reside within the private subnet. External access to private subnets is restricted; they can access the internet via a NAT gateway, but cannot be reached from the outside.