Deploying into this cluster¶
This is an ethere cluster: Kubernetes, with a number of choices already made. These pages are for whoever deploys an application into it, a person or an agent, and describe the version it runs (ethere v0.3.0-222-gecacb9979036).
In short¶
- IPv6 only. Services are
ipFamilies: [IPv6], servers listen on::. IPv4-only destinations are reached through NAT64, by name. - Every pod is denied by default, but DNS. An application declares what reaches it and what it reaches with
CiliumNetworkPolicyobjects. - Gateway API, not Ingress. An application is exposed by an
HTTPRouteon the cluster's Gateway, with a name its namespace is allowed to use; the certificate is the Gateway's. - Namespaces are granted, through git. A tenant gets its namespaces, their names and quotas, and its members'
rights from the cluster's declaration; it deploys there with its own Flux objects, whose
HelmReleasenames the service accountflux. - Nothing on a server's disk lasts. Servers are replaced at every update; data lives in volumes.
The pages¶
- Getting started: from nothing to an application served, the request for a namespace.
- Ethere's choices: each choice, why, and what it changes for manifests written elsewhere.
- Network: IPv6, NAT64, the default policies, what to allow.
- Exposing an application: the Gateway, the names, the certificates.
- Deploying: Flux in a tenant's namespace.
- Images: where images come from.
- Storage: volumes.
- Access: getting a kubeconfig, what being authenticated adds.
- This cluster: its own pages, by its admins (when it has some): who they are, the domains it offers, how to ask for a namespace.
Reading these pages¶
- People: this site, on
docs.and the cluster's zone. - Agents:
llms.txtlists every page as Markdown (<page>.md, e.g.index.md). - With a kubeconfig:
kubectl -n kube-public get configmap ethere-docs -o jsonpath='{.data.index\.md}', and a namespace's own page,kubectl -n <namespace> get configmap ethere-docs -o jsonpath='{.data.index\.md}'.