tailscale/cmd/k8s-operator/deploy/manifests
Tom Proctor cab2e6ea67
cmd/k8s-operator,k8s-operator: add ProxyGroup CRD (#13591)
The ProxyGroup CRD specifies a set of N pods which will each be a
tailnet device, and will have M different ingress or egress services
mapped onto them. It is the mechanism for specifying how highly
available proxies need to be. This commit only adds the definition, no
controller loop, and so it is not currently functional.

This commit also splits out TailnetDevice and RecorderTailnetDevice
into separate structs because the URL field is specific to recorders,
but we want a more generic struct for use in the ProxyGroup status field.

Updates #13406

Signed-off-by: Tom Proctor <tomhjp@users.noreply.github.com>
2024-09-27 01:05:56 +01:00
..
nameserver cmd/{k8s-operator,k8s-nameserver},k8s-operator: update nameserver config with records for ingress/egress proxies (#11019) 2024-05-02 17:29:46 +01:00
templates cmd/k8s-operator: generate static kube manifests from the Helm chart. (#10436) 2023-12-04 10:18:07 +00:00
authproxy-rbac.yaml cmd/k8s-operator: allow to install operator via helm (#9920) 2023-10-30 18:18:09 +00:00
operator.yaml cmd/k8s-operator,k8s-operator: add ProxyGroup CRD (#13591) 2024-09-27 01:05:56 +01:00
proxy.yaml cmd/k8s-operator/deploy/manifests: check if IPv6 module is loaded before using it (#11867) 2024-04-29 21:12:23 +01:00
userspace-proxy.yaml cmd/k8s-operator,k8s-operator: optionally serve tailscaled metrics on Pod IP (#11699) 2024-04-26 08:25:06 +01:00