gws render

Print the Kubernetes manifests gws generates from gws.json — generate-only, no cluster needed. Use it to see exactly what gws up would apply, diff manifests across profiles, or feed the output into other tooling.

You never hand-write these manifests: they're derived from gws.json in memory. gws render is the window into that generation step.

Usage

gws render [service] [options]

Argument	Description
[service]	Render only this service (default: all services).

Flag	Description
-p, --profile <name>	Configuration profile to apply before rendering.
-n, --namespace <ns>	Namespace to render into (default: <project>-render).

Because it's generate-only, gws render doesn't need an active deployment, a cluster, or a login — it reads gws.json and prints YAML.

Examples

# Render every service's manifests
gws render

# Render just the api service
gws render api

# Render as the 'ci' profile would produce them
gws render --profile ci

# Render into an explicit namespace
gws render --namespace my-preview

See also

• gws up — actually apply the generated manifests to a cluster
• gws schema — the JSON schema gws.json is validated against
• gws.json overview — the source these manifests are generated from