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 support enhanced with #293
• Vulnerability scans enhanced

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-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.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 mtCallback or Callback scopes.
• 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 activeDeadlineSeconds for 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

v0.18.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 flexible DNS configuration in Domain & ClusterDomain with #245
• Fix to prevent deletion of latest Ready application version during version monitoring/cleanup with #247
• Minor code refactoring to avoid some unused/unnecessary checks

Others

• Dependencies updated
• Documentation and website updated

Full Changelog: v0.17.0...v0.18.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.18.0/crd.yaml

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 ClusterDomain and Domain and move away from former CAPApplication --> Domains for 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