Releases: SAP/cap-operator
v0.17.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
- Added support for additional CA certificates in Domain & ClusterDomain with #240
- Service Operation metrics added
- CAPTenant: Additional tenant info added with #239
Others
- Dependencies updated
- Documentation and website updated
- Workflow - Docker Image builds for PR
Full Changelog: v0.16.0...v0.17.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.17.0/crd.yaml
v0.16.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
- Removed web-hook validation introduced in 0.15.0 for tenant operation workload names
- Service Operation metrics added
Others
- Dependencies updated
- Documentation and website updated
Full Changelog: v0.15.0...v0.16.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.16.0/crd.yaml
v0.15.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
- This release primary focused on Domain Management enhancements, to enable flexible networking configurations.
- There is an automatic migration in place via our web-hook (which should be kept enabled) which can support in the short term. However, consumers are advised to make adjustments to their application manifests (e.g. helm charts) by consuming the new CAP Operator resources
ClusterDomainandDomainand move away from formerCAPApplication --> Domainsfor networking related configurations. .
Caution
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.
Others
- Dependencies updated
- Documentation and website updated
- Pipeline: Multi-arch docker builds improved
Full Changelog: v0.14.1...v0.15.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.15.0/crd.yaml
v0.14.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
Fixes/Updates
- VirtualService hash calculation amended for Services Only workloads with #186
- Service Workloads: Documentation added with #182
Others
- Dependencies updated
Full Changelog: v0.14.0...v0.14.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-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.14.1/crd.yaml
v0.14.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
Features/Updates
- This release adds support for service workloads and Services Only scenario with #179. For more details visit the Services Only Applications documentation page.
Others
- Go Dependencies updated
Full Changelog: v0.13.0...v0.14.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.14.0/crd.yaml
v0.13.0
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: Gardener Certificate handling amended with #178
Others
- Go Dependencies updated
Full Changelog: v0.12.0...v0.13.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.13.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.
v0.12.0
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.
v0.11.1
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
- This release just contains minor patches
Others
- Go version and Dependencies updated
- minor typos
Full Changelog: v0.11.0...v0.11.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-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.11.1/crd.yaml
Caution
istio version >= 1.22 (that supports v1 API) is necessary from 0.11.0 release onwards as mentioned in our prerequisites.
v0.11.0
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: Basic Metrics enabled with #152
- Operator: Typed Workqueue used
- Container
argssupported for version workloads with #145 - Operator: Networking - istio v1 APIs used with #150
Others
- Go version and Dependencies updated
- Operator: Errors in workloads logged
- Documentation updated
Full Changelog: v0.10.0...v0.11.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.11.0/crd.yaml
Caution
istio version >= 1.22 (that supports v1 API) is necessary from this release onwards as mentioned in our prerequisites.
v0.10.0
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
Others
- Go version and Dependencies updated
- Documentation updated
Full Changelog: v0.9.0...v0.10.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.10.0/crd.yaml