cmcc-v1.13.0

CoreMedia Content Cloud through cmcc-operator

cmcc-operator-v1.13.0

Kubernetes Operator to bring up a CoreMedia Content Cloud installation

Improve configurability

• Make URL Mapping configurable per site mapping
• Allow specifying license secret name
• Make images for monogdb, mysql, and overview configurable
• Make podSecurityContext and securityContext configurable

cmcc-v1.13.0-beta.2

CoreMedia Content Cloud through cmcc-operator

cmcc-operator-v1.13.0-beta.2

Kubernetes Operator to bring up a CoreMedia Content Cloud installation

Update to io.javaoperatorsdk:operator-framework-spring-boot-starter:5.1.0

This also updates most dependencies to current versions.

Two changes had to be made: the Reconciler now implements slightly different interfaces, and implements them differently, and the Secret resource now always has a map for stringData, which is empty if the data has not been decoded from base64.

cmcc-v1.13.0-beta.1

CoreMedia Content Cloud through cmcc-operator

cmcc-operator-v1.13.0-beta.1

Kubernetes Operator to bring up a CoreMedia Content Cloud installation

Allow configuring Ingress response timeouts

The Ingress controller typically waits a specific time for the backend service to start sending a response. Once this timeout is exceeded, an error message is returned. For some applications, it might be necessary to increase that timeout. with.responseTimeout.live, with.responseTimeout.preview, and with.responseTimeout.studio allow specifying the desired timeout in seconds for the respective Ingress resources.

cmcc-v1.12.7

CoreMedia Content Cloud through cmcc-operator