Resource: yet_cloud_runtime
How things run on a server: k3s, Docker, or native. A k3s runtime goes behind a Cloudflare tunnel of its own by itself, when Cloud's edge is set — tunnel says otherwise.
Note: Opening or closing its tunnel is a Cloud admin's, and changes its ingress: its environments' records follow it.
Example Usage
resource "yet_cloud_runtime" "k3s" {
name = "box-k3s"
stack = "local:traefik+k3s"
server_id = yet_cloud_server.box.id
}Schema
Required
name(String) Its name: lowercase letters, digits and dashes, up to 32, starting with a letter.server_id(String) The server it runs on.stack(String) How it runs:local:traefik+k3s,local:dockerorlocal:native.
Optional
ingress(String) The address its environments' records point at: an IP or a name. Its tunnel's while it has one.tunnel(Boolean) Whether it is behind a Cloudflare tunnel of its own — its edge. A k3s runtime is, made while Cloud's edge is set, unless this says otherwise; only k3s runtimes have one, for now.
Read-Only
id(String) The ID of this resource.pool_id(String) The pool it is a member of, if any — set on yet_pool.rack_id(String) Its server's rack.status(String) How it stands, as Cloud shows it.tunnel_id(String) Its Cloudflare tunnel, when it has one.
Import
In Terraform v1.5.0 and later, with an import block:
import {
to = yet_cloud_runtime.k3s
id = "01J9Z8K3V7Q2M4N6P8R0S2T4V6"
}With terraform import:
terraform import yet_cloud_runtime.k3s 01J9Z8K3V7Q2M4N6P8R0S2T4V6