Skip to main content
Version: 1.42

Okteto Bring Your Own Cloud (BYOC)

Okteto Bring Your Own Cloud (BYOC) runs Okteto on your own cloud infrastructure, fully managed by Okteto.

This is ideal for teams who need to meet strict security or compliance requirements, operate at high-scale, require custom infrastructure configurations, or simply want to maintain full control over their environments with a SaaS-like experience.

We support BYOC on:

The BYOC Model​

With BYOC, you bring the cloud provider account, and we bring the platform and the operational expertise.

  • You provision and secure the cloud account
  • Okteto creates all the cloud infrastructure and software components it needs
  • Our team manages and maintains Okteto on your cloud, including upgrades, monitoring, and incident response
  • You keep full ownership of your cloud environment and data

Okteto's Commitments​

When you connect your cloud to Okteto:

  • Okteto installs and manages its components in your cloud
  • Our team handles upgrades, patching, and observability for Okteto services
  • You keep full control of your cluster and data. Okteto only interacts with the workloads our platform needs to function
  • Our team continuously monitors Okteto services
  • Our team provides support and guidance throughout your journey

Cluster Management Restrictions​

Don't modify cluster infrastructure manually in your cloud provider's console or CLI, even though you have the permissions to do it.

Resources You Must Not Modify​

  • Kubernetes cluster configuration (node pools, machine types, disk sizes, and so on)
  • Resources in Okteto-managed namespaces (including okteto, default, and system namespaces)
  • Infrastructure managed by Okteto's configuration management
  • Load balancers, networking, or storage resources created by Okteto

Risks of Manual Changes​

Manual changes to cluster infrastructure cause several serious problems:

  1. Infrastructure state conflicts: Okteto manages your cluster infrastructure with an automated daily reconciliation. Manual changes create state inconsistencies that can cause:

    • Automatic reversion of your changes during the next reconciliation
    • Configuration management failures that block critical updates
    • Unintended resource deletions or recreations
  2. SLA and support impact: When you modify infrastructure directly, Okteto can't guarantee our SLA commitments. Fixing the resulting issues may fall entirely on your side, outside our control.

  3. Missing context: Okteto's infrastructure configuration follows specific architectural decisions and requirements. Manual changes made without this context can cause unexpected side effects or service degradation.

  4. Monitoring and alerting: Direct changes can trigger false alerts for our SRE team and hide real issues that need attention.

Requesting Infrastructure Changes​

If you need infrastructure changes or want to install additional tools:

  • Contact Okteto first: reach out to your Okteto representative or support team
  • We coordinate the change through the proper channels to make sure it's compatible with our managed infrastructure
  • We implement approved changes through our infrastructure management tooling to keep it consistent

If you want to manage the infrastructure yourself, BYOC isn't the right fit. With BYOC, Okteto manages the cluster, and you keep ownership of the cloud account and data.

Log Access​

In Okteto Bring Your Own Cloud (BYOC), log access depends on the cloud provider. Besides the log views available to Okteto users, anyone with access to the cloud provider's logging solution for the account or project can review the logs forwarded there for some or all workloads in the cluster. The logs are stored in the default locations of each logging service. You can filter them by namespace, node, pod, and similar resource attributes, with labels or the service's query system.

AWS​

On AWS, Okteto BYOC sends all cluster logs to Amazon CloudWatch Logs. Inspect CloudWatch when you need workload, application, or cluster-level logs directly from AWS. The logs are stored in CloudWatch Logs log groups in the same AWS account and Region, commonly under the EKS and Container Insights log groups, such as /aws/eks/<cluster>/cluster and /aws/containerinsights/<cluster>/....

The AWS setup for BYOC grants Okteto the access it needs to operate the platform, as the AWS BYOC onboarding guide describes. To review workload logs in CloudWatch, use your own AWS access.

GCP​

On GCP, Okteto BYOC sends the system logs and the logs from the okteto namespace to Google Cloud Logging. Sending all cluster logs to Cloud Logging is opt-in: ask your Okteto technical contact to activate it. The logs are stored in Cloud Logging log buckets, typically the system-managed _Default and _Required buckets.

The current GCP BYOC onboarding flow grants Okteto administrative access in your project, as the GCP BYOC onboarding guide describes. To review the system logs and the okteto namespace logs in Cloud Logging, use your own GCP access.

Getting Started​

The BYOC onboarding guide for each cloud provider lists the steps to get started: