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
- Server: subscription domain via payload supported with #352
- Operator: temporary migration scripts removed
- Domains: Error handling amended with #357
Others
- Website & Documentation Updated.
- Update to latest Go version.
- Dependencies updated.
Full Changelog: v0.25.0...v0.26.0
Check out What's new page.
Caution
Applicable when Upgrading from below v0.15.0
The automatic migration routine described [here ](https://sap.github.io/cap-operator/docs/usage/domain-management/#automatic migration-during-upgrade) was available from [v0.15.0](https://github.com/SAP/cap-operator/releases/tag/v0.15.0) through [v0.25.0](https://github.com/SAP/cap-operator/releases/tag/v0.25.0) and has been removed now. If you need this migration, first upgrade to v0.25.0 (or lower), allow the migration to complete, and then upgrade to the latest release.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.26.0/crd.yaml