Releases: SAP/cap-operator
Release list
v0.32.0
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:
- Rollout on Credential Update Enabled with #444
- Secret Finalizers dropped with #453 (this anyway did not work as expected)
- several minor improvements
Others
- Website & Documentation Updated.
- Dependencies updated.
Full Changelog: v0.31.0...v0.32.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.32.0/crd.yaml
v0.31.0
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:
- Provider Tenant creation omitted with #430
- With this change the CA.Spec.Provider is also deprecated - TenantOperation is now always Required for multi-tenant apps with #431
- Improvements to reconciliation and other minor enhancements.
- Overall improvements to webhook handling and some enhanced validations.
Others
- Website & Documentation Updated.
- Actions/Dependencies updated.
Full Changelog: v0.30.0...v0.31.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.31.0/crd.yaml
v0.30.0
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:
- Allow
CAPApplicationVersioncleanup without a Prometheus connection with #416 - Subscription Dependency handling amended with #409
- Application: non-migrated tenants handled with #418
Others
- Website & Documentation Updated.
- Actions/Dependencies updated.
Full Changelog: v0.29.1...v0.30.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.30.0/crd.yaml
v0.29.1
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
Patch:
- We fixed an issue where credentials with metadata were accidentally not considered with #407
Highlights from 0.29.x below:
Operator:
- Subscription: getDependencies implemented with #116
- Version: Deployments startupProbe supported with #399
- CAV: version validation regex added with #389
- Version Affinity - support for multiple previous versions with #379
- Reconciles: secret creation amended with #403
- Operator: RateLimiting configured with #405 (will be made user configurable in upcoming releases)
- Operator: minor improvements for providerSubaccountId
- Misc Quality & reconciliation enhancements
Others
- Website & Documentation Updated.
- Dependencies updated.
Full Changelog: v0.29.0...v0.29.1
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.29.1/crd.yaml
v0.29.0
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:
- Subscription: getDependencies implemented with #116
- Version: Deployments startupProbe supported with #399
- CAV: version validation regex added with #389
- Version Affinity - support for multiple previous versions with #379
- Reconciles: secret creation amended with #403
- Operator: RateLimiting configured with #405 (will be made user configurable in upcoming releases)
- Operator: minor improvements for providerSubaccountId
- Misc Quality & reconciliation enhancements
Others
- Website & Documentation Updated.
- Dependencies updated.
Full Changelog: v0.28.0...v0.29.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.29.0/crd.yaml
v0.28.0
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: AppId handling enhanced
globalAccountIdis now deprecated with #338 - Misc Quality enhancements with #377
Others
- Website & Documentation Updated.
- Dependencies updated.
- Actions updated.
Full Changelog: v0.27.0...v0.28.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.28.0/crd.yaml
v0.27.0
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
- Deployments: HorizontalPodAutoscaler config enabled with #366
- Deployments: Stickiness config enabled with #371
- Operator: Version error handling improved with #372
- Tenant: Cleanup of old operation fixed with #364
Others
- Website & Documentation Updated.
- Update to latest Go version.
- Dependencies updated.
Full Changelog: v0.26.0...v0.27.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.27.0/crd.yaml
v0.26.0
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
v0.25.0
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: Queue configuration supported with #347
- Operator: istio sidecar label/annotations removed with #345
- Informers: queue mapping updated with #351
Others
- Print columns updated
- Website & Documentation Updated.
- Update to latest Go release.
- Dependencies updated.
- Workflows update
Full Changelog: v0.24.0...v0.25.0
Check out What's new page.
Caution
Applicable when Upgrading from below v0.15.0
Before upgrading, please beware that there may be a temporary outage while moving over to the new networking resources (that happens automatically during start-up of our controller). The switchover to new domain management usually happens automatically in a matter of seconds and so may not even be noticeable. However, in some cases the recreation of domain related resources may take a few mins to fully complete and so you may notice the managed application isn't reachable in that time. So please plan the upgrade accordingly.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.25.0/crd.yaml
v0.24.0
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: App Identification enhanced with #331
Others
- WebhookHandler: Enhance validation to treat nil and empty slices/maps as equal
- Website & Documentation Updated
- Update to latest go patch version.
- Dependencies updated.
Full Changelog: v0.23.0...v0.24.0
Check out What's new page.
Caution
Applicable when Upgrading from below v0.15.0
Before upgrading, please beware that there may be a temporary outage while moving over to the new networking resources (that happens automatically during start-up of our controller). The switchover to new domain management usually happens automatically in a matter of seconds and so may not even be noticeable. However, in some cases the recreation of domain related resources may take a few mins to fully complete and so you may notice the managed application isn't reachable in that time. So please plan the upgrade accordingly.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.24.0/crd.yaml