fakecloud-k8s 0.17.0

Shared Kubernetes backend primitives for FakeCloud (client bootstrap, Pod lifecycle, exec, reaping, naming, backend selection)
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30

//! Shared Kubernetes-backend primitives for FakeCloud.
//!
//! FakeCloud can run its container-backed services (Lambda, ElastiCache,
//! RDS, ECS) either by shelling out to a local Docker/Podman daemon (the
//! default) or by spawning native Pods in a Kubernetes cluster. The k8s
//! path is the same for every service — connect a client, build a Pod,
//! wait for it to come up, optionally `exec` into it, tear it down, and
//! reap orphans left by a previous process. This crate holds that common
//! machinery so each service only has to describe *its* Pod, not
//! re-implement the client bootstrap, readiness polling, exec plumbing,
//! reaping, and DNS-safe naming.
//!
//! Backend selection (`FAKECLOUD_CONTAINER_BACKEND` /
//! `FAKECLOUD_<SERVICE>_BACKEND`) lives in [`backend`]. The kube client
//! wrapper and Pod lifecycle live in [`client`]. Env parsing
//! (`FAKECLOUD_K8S_*`) lives in [`env`]. Naming + label conventions live
//! in [`names`] and [`labels`].
//!
//! See `website/content/docs/guides/kubernetes-backend.md` for the
//! operator-facing setup (ServiceAccount, RBAC, Deployment yaml).

pub mod backend;
pub mod client;
pub mod env;
pub mod labels;
pub mod names;

pub use backend::{backend_choice, Backend};
pub use client::{ExecOutput, K8sClient, K8sError};
pub use env::{K8sEnv, K8sEnvError};