Releases: SAP/cap-operator
v0.9.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
- CAV Ready state handling amended (The CAV now only gets
Readyonce all relevant workloads are "ready") with #122 - webhook validations enhanced with #123
Others
- Go version and Dependencies updated
- Documentation updated
Full Changelog: v0.8.0...v0.9.0
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.9.0/crd.yaml
v0.8.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
- CAPTenantOutput introduced with #120
Others
- initContainers env. variables enhanced to include most values from main container
- Go version and Dependencies updated
- Documentation updated
Full Changelog: v0.7.0...v0.8.0
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.8.0/crd.yaml
v0.7.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
- Tenant version updates amended to be done once operations are completed with #108
- Logging enhanced overall. Now includes steps and overall message updated
Others
- Go version and Dependencies updated
- Documentation updated
Cleanup
- MTX wrapper & other temp. workarounds removed
Full Changelog: v0.6.0...v0.7.0
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.7.0/crd.yaml
v0.6.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
- initContainers supported for all workloads with #91
Others
- subscription domain made configurable with #98
- Go version and Dependencies updated
- Documentation updated
Full Changelog: v0.5.0...v0.6.0
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.6.0/crd.yaml
v0.5.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
- Enabled JSON Logs & Added/Enhanced structured logs with #77
Others
- subscriptionContext of the provider fixed with #86
- Workflows updated to the latest version with #84
- Go version and Dependencies updated
- Documentation updated
Full Changelog: v0.4.0...v0.5.0
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.5.0/crd.yaml
v0.4.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
- Subscription Context supported with #80
(Note: To get the subscription metadata part working @sap/cds-mtxs 1.18.0 or higher is required) - SaaS callback payload enhanced with #83
Others
- Structured logs used wherever possible with #73
- Go version and Dependencies updated
- Documentation updated
Full Changelog: v0.3.0...v0.4.0
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.4.0/crd.yaml
v0.3.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
- DNS_TARGET via env. supported with #68
Fixes
- DNSEntry handling amended (to avoid * in dns targets) with #70
Others
- Go version and Dependencies updated
- Documentation updated
Full Changelog: v0.2.0...v0.3.0
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.3.0/crd.yaml
v0.2.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
- Panic recovery mechanism implemented with #59
- Preserving Secrets (service credentials) implemented with #61
Fixes
- Typos in documentation fixed
Others
- Dependencies updated
- Documentation updated
Full Changelog: v0.1.0...v0.2.0
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.2.0/crd.yaml
v0.1.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
- Scheduling related configurations added with #44
- Volumes/VolumeMounts and ServiceAccountName supported with #49
Fixes
- Sticky cookie corrected in #51
Others
- Dependencies updated
- Documentation updated
- Tooling enhanced
Full Changelog: v0.0.1...v0.1.0
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.1.0/crd.yaml
v0.0.1
Welcome to the CAP Operator
The first release of CAP Operator
CAP Operator manages the lifecycle operations involved in running multi-tenant CAP applications on Kubernetes clusters, primarily SAP Gardener managed clusters.
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.0.1/crd.yaml
Full Changelog: https://github.com/SAP/cap-operator/commits/v0.0.1