Documentation
¶
Overview ¶
Package eks implements the AWS EKS REST/JSON control-plane API as a server.Handler. Point the real aws-sdk-go-v2/service/eks client at a Server registered with this handler and CreateCluster, CreateNodegroup, CreateFargateProfile, CreateAddon, and their friends work against an in-memory EKS driver.
Wave 1 covers control-plane resources only; the Kubernetes data plane (Pods, Deployments, Services, …) is out of scope and is deferred to Wave 2. Until Wave 2 ships, the cluster Endpoint field returns a placeholder URL and the CertificateAuthority field returns a stub PEM, so kubeconfig generation works syntactically without a real apiserver.
EKS uses REST/JSON (not the AWS query protocol). URL paths follow the shape the SDK emits, e.g. POST /clusters, POST /clusters/{name}/node-groups, POST /clusters/{name}/addons/{addon}/update. The handler's Matches predicate is rooted at /clusters so it does not shadow the catch-all S3 handler that may be registered alongside.
Index ¶
Constants ¶
This section is empty.
Variables ¶
This section is empty.
Functions ¶
This section is empty.
Types ¶
type Handler ¶
type Handler struct {
// contains filtered or unexported fields
}
Handler serves AWS EKS REST/JSON requests against an EKS driver.
Source Files