Skip to content

v0.3.0
Compare
Choose a tag to compare
@Pavan-SAP Pavan-SAP released this 07 Mar 10:29
· 74 commits to main since this release
v0.3.0
f90aa29
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.

Welcome to the CAP Operator

CAP Operator manages and automates the lifecycle of multi-tenant SAP Cloud Application Programming Model (CAP) based applications on Kubernetes.

The next release of CAP Operator

What's Changed

Features

  • DNS_TARGET via env. supported with #68

Fixes

  • DNSEntry handling amended (to avoid * in dns targets) with #70

Others

  • Go version and Dependencies updated
  • Documentation updated

Full Changelog: v0.2.0...v0.3.0

Documentation

Visit the Documentation to find out how to install and use the CAP Operator

Setup

The operator can be deployed using the helm chart which is part of CAP Operator Lifecycle repo.
To install the CAP Operator using the published helm chart, you may use the command(s):

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>

For details see: https://sap.github.io/cap-operator/docs/installation/helm-install/

CRDs

CRDs for the CAP Operator can be applied from the ./crds folder or the assets here in the release, these are also copied over to the helm chart.
To apply CRDs from this release version, you may use the command:

kubectl apply -f https://github.com/SAP/cap-operator/releases/download/v0.3.0/crd.yaml
Assets 3
Loading