General console settings#

Open Settings → General. The page includes AI defaults, kubectl and node-terminal enablement/images, optional resource visibility, the Cluster Agent image, analytics/version-check switches and the login prompt. Save changes through the page and verify the affected feature in a separate user workflow.

Setting areaOperational effect
Terminal enablement and imagesControls whether the console offers the feature and which helper image it uses. Kubernetes permissions and image access remain required.
Resource visibilityControls optional navigation entries; hiding a link is not an authorization rule.
Cluster Agent imageSets the image used for generated agent installation material. Match it to the release you support.
Analytics / version checkControls the corresponding optional behavior. Review external connectivity requirements for your environment.
Login promptAdds your installation’s sign-in guidance; do not include secrets in public login text.
General settings group optional integrations and console capabilities. Review the description of each control before enabling it.
General settings group optional integrations and console capabilities. Review the description of each control before enabling it. View full size ↗

Create a resource template#

  1. Open Settings → Templates and choose the create action.
  2. Set the template name and resource content using the editor. Use a minimal manifest suited to its intended kind.
  3. Save and open the New resource flow to verify the template is available.
  4. Select the template, supply the destination-specific name and namespace, and review the final YAML before creating a resource.
Create Template stores a reusable name, description and YAML document. Saving a template does not deploy a resource.
Create Template stores a reusable name, description and YAML document. Saving a template does not deploy a resource. View full size ↗

Maintain templates#

Treat templates as starting points, not live controllers. Updating a template does not update previously created objects. Remove obsolete images, environment-specific addresses and unnecessary privileges before distributing a template across teams.

If the template is missing from a create dialog, verify it was saved and that the selected resource kind and your permissions match its intended use. A template can still be rejected by Kubernetes admission when applied.