Releases: SAP/cap-operator
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
v0.23.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
- Pod Disruption Budget: workload specific configuration added with #302
- Topology Spread Constraints handling updated with #308
Others
- Minor Quality issues addressed
- Website & Documentation Updated
- Update to latest go patch version.
- Dependencies updated.
Full Changelog: v0.22.0...v0.23.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 startup 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.23.0/crd.yaml
v0.22.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
- Service Exposure enhanced to support all deployment workloads with #293
- Vulnerability scans enhanced (we now also scan our container images using Grype)
Others
- Documentation Updated
- Update to latest go patch version.
- Dependencies updated.
Full Changelog: v0.21.0...v0.22.0
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 startup 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.
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.22.0/crd.yaml
v0.21.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
- Tenant Deletion enhanced with #278
- Support version affinity after upgrade (experimental) with #260
Others
- Update to latest go patch version.
- Several Dependencies updated.
- SBOM Release artifact name updated.
Full Changelog: v0.20.1...v0.21.0
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 startup 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.
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.21.0/crd.yaml
v0.20.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
- Use latest release of prometheus operator.
Others
- SBOM Release artifact name simplified.
- Update to latest go version.
Full Changelog: v0.20.0...v0.20.1
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 startup 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.
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.20.1/crd.yaml
v0.20.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
- Add support for Subscription Manager based app subscription.
- Subscription: SaaS scope handling amended to expect one of
mtCallbackorCallbackscopes. - SubscriptionGUID metadata is now added to tenant and tenant related resources.
Others
- We now provide an SBOM with our Release , this can be used by consumers to know what is contained in our released containers.
- Dependencies updated.
- Documentation and website updated.
Full Changelog: v0.19.0...v0.20.0
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 startup 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.
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.20.0/crd.yaml
v0.19.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
- Add support for Optional Mutual tlsMode with #253
- Enable setting
activeDeadlineSecondsfor Jobs with #252
Others
- Dependencies updated
- Documentation and website updated
Full Changelog: v0.18.1...v0.19.0
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 startup 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.
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.19.0/crd.yaml
v0.18.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
- This release primarily fixes an issue with DNS entry handling
- Minor code refactoring to avoid some unused/unnecessary checks
Others
- Dependencies updated
- Documentation and website updated
Full Changelog: v0.18.0...v0.18.1
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 startup 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.
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.18.1/crd.yaml