Skip to main content
Kubernetes manifest components allow you to deploy raw Kubernetes resources using YAML manifests. To learn more about components, see the Components concept page.

Configuring a Kubernetes Manifest component

To configure a Kubernetes manifest component, specify a namespace and the manifest files to deploy.
components/kubernetes_manifest.toml

Multiple Resources in a Single Manifest

Kubernetes manifest components support multiple resources separated by the standard YAML document separator ---:
components/deployment.yaml

Using Nuon Context Variables

Kubernetes manifest components support Nuon’s templating system, allowing you to access variables and outputs from other components:
components/configmap.yaml

Common Use Cases

Deploying with Custom Images

components/app-deployment.yaml

Creating Ingress Resources

components/ingress.yaml

Using AWS Load Balancer Controller

components/nlb-service.yaml

Kustomize

In addition to inline manifests, Kubernetes manifest components can be sourced from a Kustomize overlay in a Git repo. Use this when you want to assemble your manifests from a base + overlays, layer in patches, or share manifests across multiple components.

Pointing a component at a Kustomize overlay

A Kustomize-backed component references the repo holding the overlay (either public_repo for a public GitHub repo, or connected_repo for a Nuon-connected private repo) and a kustomize.path relative to the source root.
components/kustomize-demo.toml
The directory selected by kustomize.path must contain a standard kustomization.yaml. Nuon builds the overlay into a manifest artifact during the component build.
gke-simple/src/components/kustomize-demo/kustomization.yaml

Supported Kustomize features

Nuon supports local-only Kustomize builds. The initial Git checkout configured by public_repo or connected_repo is supported, but Kustomize cannot fetch additional sources from inside that checkout’s configuration. Supported features include:
  • Local resources, bases, and components.
  • Local patches, replacements, and transformer configurations.
  • ConfigMap and Secret generators using local files, environment files, or literal values.
  • Labels, annotations, name prefixes and suffixes, image overrides, and replica counts.
  • Inline or local file-backed built-in generator and transformer configurations.
Files and symlinks must stay within the build’s checked-out source tree. Kustomize’s rootOnly load restriction is always enforced: local base directories such as ../../base can be used within that tree, but individual file inputs must also satisfy the load restriction of the Kustomization that reads them. load_restrictor = "none" is not supported. The following features are not supported:
  • Nested remote references: Git references and HTTP(S) URLs in Kustomize inputs, including resources, bases, components, patches, and generator inputs. This applies to public and private destinations alike. Vendor the required files or bases into the source tree and reference them locally instead.
  • Helm chart inflation: helmCharts, helmChartInflationGenerator, and enable_helm = true. Omit enable_helm or leave it false. Use a separate Helm chart component to deploy Helm charts.
  • Directory-backed plugin configurations: Directories listed under generators, transformers, or validators. Use a local configuration file instead of a directory that builds the configuration.
  • External executable or function plugins.
For example, keep a shared base in vendor/shared-base/ alongside the local base/ rather than referencing its Git repository or an HTTP URL:
kustomization.yaml
These restrictions keep Kustomize’s file reads within the build source and prevent its remote loaders and subprocesses from bypassing that boundary.

Template variables in Kustomize trees

Kustomize-backed components support the same {{.nuon.*}} template variables as inline manifests. Placeholders are rendered on the runner, against the live install state, after kustomize build produces the final manifest. This means you can reference install IDs, app metadata, install stack outputs, and other component outputs directly from any YAML file inside your Kustomize overlay.
gke-simple/src/components/kustomize-demo/configmap.yaml
After a deploy, the rendered ConfigMap on the cluster will have the placeholders replaced with the install’s actual values — for example, install_id: inl..., project_id: nuon-gcp-support.
Kustomize-backed manifests are templated on the runner, not in the planner. This keeps the Temporal workflow payload small even for large Kustomize trees. Inline manifests, by contrast, are still rendered in the planner.

Nuon Managed Sandbox Components

The aws-eks-sandbox managed Sandbox ships with standard components that your Kubernetes manifests can leverage: The Sandboxes are open source and can be customized, if these components do not work for your application.

Best Practices

Namespace Management

Always specify namespaces explicitly in your manifests. If not provided, it defaults to the namespace specified in the config. If both the component configuration and manifest are missing namespace specifications, the component deployment will fail:
components/namespace.yaml

Kubernetes manifest components are processed in the order they appear in your repository. If you have dependencies between resources, ensure they are ordered appropriately or use proper Kubernetes resource dependencies.