Kubernetes package v1.0.0

List the cluster's namespaces: names, phases and labels, which reveal internal tenancy topology. Per the retrieved Namespace API reference the endpoint supports label and field selectors and pagination; the registered path covers the collection read only — single-namespace reads (GET /api/v1/namespaces/{name}) are not registered by this pack.

The host is a reserved placeholder: substitute the cluster's API server endpoint before enabling.

List the Deployments in one namespace: names, replica counts, rollout strategy and the full pod template, which reveals images, volume wiring — and, according to the reviewed Pod API reference embedded in the template, literal environment-variable values, command arguments and annotations. Secret references appear by name only and are not dereferenced, but plaintext credentials written as literal env values in the template would be exposed by this read.

Per the retrieved Deployment API reference the endpoint supports label and field selectors and pagination; the registered path covers the namespaced collection read only — the cluster-wide list (GET /apis/apps/v1/deployments) and single-object reads are not registered. NAMESPACE is a placeholder the deployment binds before enabling.

List the Pods in one namespace: names, phases, container specs and status.

Data exposure: according to the reviewed Pod API reference the returned specifications include literal environment-variable values (env value fields), command and argument arrays, annotations and node placement, alongside secret and configmap references — secret values are not dereferenced by this read (secretKeyRef entries appear by name only), but a workload that carries credentials as literal env values or command arguments exposes them in this response, so the absence of dereferencing is no guarantee that no plaintext credentials are returned.

The registered path covers the namespaced collection read only — the cluster-wide list (GET /api/v1/pods), single-pod reads and pods/log are not registered; reading Secrets is a documented exclusion of this pack. NAMESPACE is a placeholder the deployment binds before enabling.

Create one Deployment in one namespace.

Judged by effect: the body is an unrestricted Deployment spec (according to the reviewed Deployment API reference) that selects container images, replica counts, the pod's service account, volume mounts including host paths, and security contexts — creating a Deployment is running caller-chosen code on the cluster — so the capability declares create and deploy at the minimum R3 tier, and deploy is one of the designated actions requiring human approval; an installer's intention to submit only benign specs is not a restriction.

The dryRun query parameter exists in the API but does not change what this registration permits. NAMESPACE is a placeholder the deployment binds before enabling.

Replace one Deployment's replica count through its scale subresource (a Scale object body, not a full Deployment spec). Registered as update and deploy at the minimum R3 tier: scaling a live workload changes running production capacity immediately — scaling to zero takes the workload offline and a large scale-up consumes cluster capacity — a deploy-equivalent reconfiguration of live infrastructure, and deploy is one of the designated actions requiring human approval; the previous replica count being re-settable does not remove the live-traffic effect.

The generic PATCH on the Deployment object is deliberately not registered (its unrestricted body would admit the same code-selection effects as creation); this registration covers the scale subresource only. NAMESPACE and NAME are placeholders the deployment binds before enabling.

Delete one Deployment; according to the reviewed Deployment API reference the call accepts a DeleteOptions body, a grace period and a propagation policy, and the default cascade deletes the Deployment's ReplicaSets and Pods with it — the running workload stops. Delete is one of the designated actions requiring human approval at the minimum R3 tier; re-applying the manifest later is a new creation, not an undo, and any pod state that was not persisted elsewhere is gone.

The deletecollection form (DELETE on the collection, bulk deletion by label selector) is deliberately not registered. NAMESPACE and NAME are placeholders the deployment binds before enabling.

Delete one namespace and, through the namespace controller, every object in it — workloads, services, configmaps, secrets and volume claims — with the namespace passing through the Terminating phase documented in the retrieved Namespace API reference while finalizers complete. This is among the most extensive operations a cluster offers; delete is one of the designated actions requiring human approval at the minimum R3 tier.

On supported execution paths mediated by AAES Govern, irreversible actions require approval by an authorized person; this does not prevent calls through bypass or observation-only paths. The /finalize subresource (which can force-remove finalizers from a stuck namespace and strand its resources) is deliberately not registered. NAME is a placeholder the deployment binds before enabling.