Skip to main content

Extra Templates

Replaced by Manifests

Extra Templates have been replaced by Manifests. The free-form Templates editor no longer exists in Project → Settings → Chart Configuration: to add or edit custom Kubernetes resources, use Manifests — each resource is its own manifest, with validation, preview and per-Workload or project-wide scope.

Extra Templates were a single free-form YAML field in the Project's Chart Configuration where you pasted extra Kubernetes resources (custom Ingresses, ConfigMaps, NetworkPolicies, test Pods…) to deploy alongside the generated chart.

What happened to your Extra Templates​

Starting with SleakOps 3.0.0, Extra Templates are deprecated and the Extra Templates of every Project were migrated to manifests automatically — the migration is compulsory and needs no action on your side. Each YAML document became one manifest:

  • A document that redefines a resource SleakOps already generates for a Workload (same kind and name — for example, your own version of a Workload's Service or Ingress) became that Workload manifest's customization: it shows as Customized in the Workload's Advanced view.
  • Every other document became a manifest in the Project's project bucket (Custom origin), which deploys with every release of the Project.

Commented-out documents were not migrated. The migrated resources deploy the same way they did before.

If the migration changed your Project's chart, you may find a pending deployment whose description says it was created by SleakOps to apply the new version; publish it like any other pending change.

What you see now​

The Chart Configuration page shows an Extra templates are managed as project manifests notice, and the section below Manifests is now Extends Values: it only holds the project global values, which you keep editing as before.

  • With Manifests enabled for your company, the notice points to the Manifests section above it, where you add and edit the migrated resources.
  • With Manifests not yet enabled for your company, the migrated resources keep deploying but are read-only until the Manifests editor is enabled — ask your SleakOps contact to enable it.

FAQs​

How do I add a custom Ingress or another custom resource now?​

Add it as a manifest — from the Workload's Advanced view (scoped to that Workload) or from the project bucket in Chart Configuration (shared across the Project). See Adding a manifest.

What types of Kubernetes resources can I deploy?​

Namespace-scoped resources only: every manifest must set metadata.namespace to the Project environment's namespace, and cluster-scoped resources (ClusterRoles, ClusterRoleBindings, CustomResourceDefinitions, PersistentVolumes, StorageClasses…) are rejected. Resources of a custom kind (CRD) are accepted, as long as the CRD is installed in the cluster.

Where are my custom values now?​

In the Values editor of the Extends Values section of Chart Configuration — they were not changed by the migration. See Values.