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/Updates
- Operator: RestartPolicy handling added with #161
- Operator: jwt validation dependants updated with #172
- Operator: slices usage amended with #175
- Operator: CRD(s)/Type(s) updated with #168
Others
- Go version and Dependencies updated
- Documentation/website updated
Full Changelog: v0.11.1...v0.12.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-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.12.0/crd.yaml
Caution
istio version >= 1.22 (that supports v1 API) is necessary from 0.11.0 release onwards as mentioned in our prerequisites.