Releases: application-stacks/runtime-component-operator
1.4.1
Install instructions are here. See the new user guide for more information on how to use the Runtime Component Operator.
Runtime Component Operator 1.4.1 includes the following features and changes:
- Optimizes reconciliation time by continuously analyzing the status of instances and reconciliation events and then auto-tuning the reconciliation process. This is enabled by default and should benefit most workloads, but it can be fine-tuned as necessary by using the configuration options supported by the Operator.
- Added support to various logging levels to gather information and insights of the Operator. The amount of logs that are written with the default ‘info’ log level has been reduced.
- Included security fix updates for Go, operating system packages and API libraries.
1.4.1-rc.1
Do NOT use in production. For internal testing only.
1.4.0
Install instructions are here. See the new user guide for more information on how to use the Runtime Component Operator.
Runtime Component Operator 1.4.0 includes the following features and changes:
- Support for DNS configurations is added.
- Support for tolerations to allow the scheduler to schedule pods on nodes with matching taints is added.
- The Runtime Component Operator sets
RuntimeDefault
as the default value of the seccomp profile. - Additional DNS entries in the certificate for the applications including for StatefulSet and headless service are added. New certificates will be generated for the applications that utilize the
.spec.manageTLS
functionality. - API and Library updates; Security vulnerabilities fixes
1.4.0-rc.1
Do NOT use in production. For internal testing only.
1.3.3
Install instructions are here. See the new user guide for more information on how to use the Runtime Component Operator.
Runtime Component Operator 1.3.3 includes the following features and changes:
- New configuration option
.spec.disableServiceLinks
to control service links - Support for Red Hat OpenShift Container Platform 4.16 and Kubernetes 1.29
- Reduce restrictions on common name in an Application’s certificate
- API and Library updates
- Security vulnerability fixes
1.3.2
Install instructions are here. See the new user guide for more information on how to use the Runtime Component Operator.
Runtime Component Operator 1.3.2 includes the following features and changes:
-
Enhancements to viewing application status:
- Include observed generation information (
.status.observedGeneration
) to verify the successful reconciliation of CR updates. - Output additional warnings for invalid user configurations (i.e. service port is
9080
when.spec.manageTLS
is enabled).
- Include observed generation information (
-
Increased Operator memory limit to
1Gi
to allow management of larger estate of applications. -
Configuration option to control mounting of ServiceAccount token (
.spec.serviceAccount.mountToken
) applies to Knative service (serverless) when.spec.createKnativeService
is enabled. -
Create Route with accurate host information when it is reset.
-
Allows to specify ServiceAccount with a name same as Operator’s default ServiceAccount (
.spec.serviceAccount.name
). -
Updates to Kubernetes APIs, go and other libraries.
-
Security vulnerabilities fixes.
-
Switched to the strategic File-Based Catalog (FBC).
- FBC provides more flexibility in organizing the content of the catalog as well as in managing Runtime Component Operator's upgrade graph.
1.3.2-rc.1
Do NOT use in production. For internal testing only.
1.3.1
1.3.1-rc.1
For internal testing only. Do not use in production.
1.3.0
Install instructions are here. See the new user guide for more information on how to use the Runtime Component Operator.
- Enhancements for high availability and scaling of applications across multiple availability zones
- Support for OpenShift 4.14 and Kubernetes 1.27
- Updates to Operator SDK, Kubernetes APIs and other libraries
- Security vulnerabilities fixes