Welcome to the CAP Operator
CAP Operator manages and automates the lifecycle of multi-tenant SAP Cloud Application Programming Model (CAP) based applications -or- Services-Only applications on Kubernetes.
The next release of CAP Operator
What's Changed
Operator:
- providerSubaccountId is now mandated with #496
- App: Provider tenant auto deleted with #503
- Enhance secret readiness message for CAPApplication and CAPApplicationVersion with #493
- several minor improvements
Others
- Website & Documentation Updated.
- Go version and Dependencies updated.
Full Changelog: v0.34.0...v0.35.0
Check out What's new page.
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/
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.35.0/crd.yaml