This is the multi-page printable view of this section. Click here to print.

Return to the regular view of this page.

Using Helm

How to deploy with Helm charts

To install CAP Operator components, use the Helm chart published as an OCI package at oci://ghcr.io/sap/cap-operator-lifecycle/helm/cap-operator.

Installation

Create a namespace and install the Helm chart in that namespace by specifying the domain and dnsTarget for your subscription server, either:

  • As command line parameters:

    kubectl create namespace cap-operator-system
    helm upgrade -i -n cap-operator-system cap-operator oci://ghcr.io/sap/cap-operator-lifecycle/helm/cap-operator --set subscriptionServer.domain=cap-operator.<CLUSTER-DOMAIN> --set subscriptionServer.dnsTarget=public-ingress.<CLUSTER-DOMAIN>
    
  • As a YAML values file:

    kubectl create namespace cap-operator-system
    helm upgrade -i -n cap-operator-system cap-operator oci://ghcr.io/sap/cap-operator-lifecycle/helm/cap-operator -f my-cap-operator-values.yaml
    

    The values file my-cap-operator-values.yaml can have the following content:

    subscriptionServer:
      dnsTarget: public-ingress.<CLUSTER-DOMAIN>
      domain: cap-operator.<CLUSTER-DOMAIN>
    

Optional steps

  • Enable Service Monitors for metrics

    To enable monitoring via metrics emitted by CAP Operator components, set the following value:

    monitoring:
      enabled: true # <-- enables creation of service monitors for metrics emitted by CAP Operator components
    

    To enable detailed operational metrics for the controller:

    controller:
        detailedOperationalMetrics: true
    
  • Set up Prometheus integration for Version Monitoring

    To use the Version Monitoring feature, provide a Prometheus server URL to the CAP Operator. When installing with the Helm chart, specify the following values:

    controller:
      versionMonitoring:
        prometheusAddress: "http://prometheus-operated.monitoring.svc.cluster.local:9090" # <-- example of a Prometheus server running inside the same cluster
        promClientAcquireRetryDelay: "2h"
        metricsEvaluationInterval: "30m" # <-- interval at which version metrics are evaluated
    

    On startup, the controller attempts to connect to the Prometheus server and fetch runtime information to verify the connection. If the connection fails, it retries after the delay specified in controller.versionMonitoring.promClientAcquireRetryDelay. See default values here.

1 - Helm Values

Discover all values supported by the latest CAP Operator helm chart