The base platform
Every environment gets the base platform (base-platform), whether Ryvn built the cluster or you
connected an existing one:
- The Ryvn Agent, which runs deployments and reports state back to Ryvn
- The Ryvn collector and kube-state-metrics, which forward logs and metrics to Ryvn
- KEDA, for event-driven autoscaling
The managed runtime
When Ryvn provisions the environment in AWS, Google Cloud, or Azure, the environment’s platform blueprint isaws-platform, gcp-platform, or
azure-platform. It builds the cluster and its network, includes the base platform, and adds the components that
servers and jobs rely on:
The platform blueprint also publishes the environment’s network details, such as the VPC and private subnets, so other
blueprints can create cloud resources inside that network.
What depends on it
These features need the managed runtime, so they’re documented in the Managed runtime tab:- Servers and jobs. Ryvn builds the container, deploys it, and runs its pre-deploy command and health checks. See Servers and Jobs.
- Networking. Exposing a port, domains and TLS, routes, and outbound IPs use the managed gateway, cert-manager, and external-dns. See Networking.
- Autoscaling and node pools. Scaling servers on CPU and memory, and adding nodes for them, uses the node autoscaler and resource metrics. See Scaling.
- Managed datastores. The Postgres, cache, and bucket blueprints create cloud resources in the environment’s network, so they need the network details only a Ryvn-provisioned environment publishes.