Package Supporting Configuration (Manifests)

< Helm Configuration Overview

Your package may need additional configuration not included in its Helm Chart but required for its functionality. For example, a package deploys cert-manager and needs to configure solvers using the cert-manager ClusterIssuer resource.

You can use template variables to create dynamic manifests.

note

• Each manifest represents a single Kubernetes resource in the target cluster.
• Manifests are created in the same namespace as the package, unless they are cluster-wide resources.

Web Interface Instructions

Steps

• Use the Text editor to enter the yaml manifest. See example template.
• Click the +Add Manifest button to add more manifests. You can add as many as you need.
• Click the Continue button.

Screenshot(s):

What comes next?

• Review the Configuration Summary

Related Reading

• Learn how to use Wayfinder's System Variables
• Learn about configuring Default Helm Charts
• Learn about configuring Static Helm Charts
• Learn about configuring Dynamic Helm Charts

Examples

apiVersion: cert-manager.io/v1
kind: ClusterIssuer
metadata:
  name: le-prod
spec:
  acme:
    email: cert-expiry@myorg.io
    server: https://acme-v02.api.letsencrypt.org/directory
    privateKeySecretRef:
      name: le-prod
    solvers:
    {{- range .Cluster.DNSZones }}
    {{- if not .Private }}
    - dns01:
      {{- if .AWS }}
        route53:
          region: {{ .AWS.Region }}
          hostedZoneID: {{ .ZoneID }}
      {{- end }}
      {{- if .Azure }}
        azureDNS:
          subscriptionID: {{ .Azure.Subscription }}
          resourceGroupName: {{ .Azure.ResourceGroup }}
          hostedZoneName: {{ .Domain }}
      {{- end }}
      {{- if .GCP }}
        cloudDNS:
          project:  {{ .GCP.Project }}
          hostedZoneName: {{ .ZoneID }}
      {{- end }}
      selector:
        dnsZones:
        - {{ .Domain }}
    {{- end }}
    {{- end }}
    - http01:
        ingress:
          class: external
          serviceType: ClusterIP