Skip to content

v0.23.0

Latest
Latest

Choose a tag to compare

View all tags
@Pavan-SAP Pavan-SAP released this 11 Dec 10:02
· 10 commits to main since this release
v0.23.0
This tag was signed with the committer’s verified signature.
Pavan-SAP Pavan
GPG key ID: FC9CF4155D07B544
Verified
Learn about vigilant mode.
5f3e031
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

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
Assets 6
Loading