Apicurio Registry Operator 1.1.3-v2.6.4.final

Installation

You can install Apicurio Registry Operator using:

• OperatorHub (also available on OpenShift)
• Install file from the distribution archive that is attached to the corresponding GitHub release. Follow the instructions in the included README file.
• Install file from the Apicurio Registry Operator repository.

Features

• Deployed Apicurio Registry version is 2.6.4.Final.

• Fix: PTS (podTemplateSpec) change not detected when Deployment is deleted or edited.

• Fix: Initialization check failing due to cyclic redirect.

• Fix: Env. variables not applied when Deployment is deleted. Improve detection of when Deployment does not contain correct env. variables. Remove deprecated feature that allowed users to manually edit Deployment to specify env. variables - this has caused the code to be more complex and increased chance of bugs, and is not feasible to support it together with the PTS feature.

• Improve panic messages

• Fix: Update Quarkus HTTP TLS options. With a Quarkus version upgrade, the supporting TLS options have changed. It no longer uses quarkus.http.ssl.certificate.key-file and quarkus.http.ssl.certificate.file, but *.files. See https://quarkus.io/guides/http-reference#configuring-the-http-server-directly .

This list may not be exhaustive. For more details, review the documentation included in the distribution archive or at Apicurio Registry documentation page (select the appropriate Apicurio Registry Operator version in the lower left corner).

Apicurio Registry Operator 1.1.2-v2.5.11.final

Installation

You can install Apicurio Registry Operator using:

• OperatorHub (also available on OpenShift)
• Install file from the distribution archive that is attached to the corresponding GitHub release. Follow the instructions in the included README file.
• Install file from the Apicurio Registry Operator repository.

Features

• Deployed Apicurio Registry version is 2.5.11.Final.

• Handle the JAVA_OPTIONS variable name change in a backwards compatible way. Requiring the user to change the variable name causes issues when automatic OLM updates are enabled. This update ensures that the operator translates use of JAVA_OPTIONS to JAVA_OPTS_APPEND automatically. Users are still encouraged to rename the variable.

• Update descriptions in the CSV, add new annotations required by Kubernetes and Openshift.

This list may not be exhaustive. For more details, review the documentation included in the distribution archive or at Apicurio Registry documentation page (select the appropriate Apicurio Registry Operator version in the lower left corner).

Apicurio Registry Operator 1.1.1-v2.5.9.final

Installation

You can install Apicurio Registry Operator using:

• OperatorHub (also available on OpenShift)
• Install file from the distribution archive that is attached to the corresponding GitHub release. Follow the instructions in the included README file.
• Install file from the Apicurio Registry Operator repository.

Features

• Deployed Apicurio Registry version is 2.5.9.Final.

• The JAVA_OPTIONS environment variable no longer works as expected. You can use the JAVA_OPTS_APPEND environment variable instead. The JAVA_OPTS environment variable is also available, which replaces the default content of Java options. However, it is best to append using the JAVA_OPTS_APPEND environment variable if possible. Apicurio Registry Operator has been updated to use the new environment variables.

• Apicurio Registry Operator supports configuration of the SQL data source using environment variables, as an alternative to the spec.configuration.sql.dataSource fields in the ApicurioRegistry custom resource. This allows users to provide SQL credentials using Kubernetes secrets instead of in plaintext.

  Apicurio Registry Operator has been improved in this version to better support this use case. Users are now able to use both the spec.configuration.sql.dataSource and spec.configuration.env fields to define parts of the configuration. For example, this is now valid:

  apiVersion: registry.apicur.io/v1
  kind: ApicurioRegistry
  metadata:
    name: myregistry
  spec:
    configuration:
    persistence: sql
    sql:
      dataSource:
        url: "jdbc:postgresql://..."
        userName: "postgres-user"  
    env:
      - name: REGISTRY_DATASOURCE_PASSWORD
        valueFrom:
        secretKeyRef:
          name: postgres-secret
          key: password

  Apicurio Registry Operator detects this type of configuration and applies it immediately without a need for additional user intervention.

• Updated version of go to 1.20.

• Updated dependency versions.

This list may not be exhaustive. For more details, review the documentation included in the distribution archive or at Apicurio Registry documentation page (select the appropriate Apicurio Registry Operator version in the lower left corner).

Apicurio Registry Operator 1.1.0-v2.4.12.final

Installation

You can install Apicurio Registry Operator using:

• OperatorHub (also available on OpenShift)
• Install file from the distribution archive that is attached to the corresponding GitHub release. Follow the instructions in the included README file.
• Install file from the Apicurio Registry Operator repository.

Features

• Deployed Apicurio Registry version is 2.4.12.Final.

• Support Kubernetes 1.25 by working with both v1beta1 and v1 versions of PodDisruptionBudget.

• Support configuration of custom environment variables for Apicurio Registry using spec.configuration.env field in the ApicurioRegistry CR.

• You can provide a secret containing a TLS certificate and key using spec.configuration.security.https.secretName field, and Apicurio Registry Operator will configure Apicurio Registry to support HTTPS connections on port 8443.

• You can set log level for non-library Apicurio Registry components separately using spec.configuration.registryLogLevel field.

• You can set log level for the Apicurio Registry Operator by configuring an environment variable LOG_LEVEL in its Deployment. Supported values are debug, info (default), warn, and error.

• Support configuring custom affinity, tolerations, and image pull secrets, using the spec.deployment.affinity, spec.deployment.tolerations, and spec.deployment.imagePullSecrets fields, respectively.

• You can configure custom Apicurio Registry image using the spec.deployment.image field.

• Support configuring custom annotations and labels for the Apicurio Registry pod using spec.deployment.metadata.annotations and spec.deployment.metadata.labels fields.

• You can prevent Apicurio Registry Operator from managing the following resources:

  • Ingress
  • NetworkPolicy
  • PodDisruptionBudget

  in case you need to manage them yourself, using spec.deployment.managedResources.* fields.

• The ApicurioRegistry CRD now contains the spec.deployment.podTemplateSpecPreview field, which has the same structure as the field spec.template in a Kubernetes Deployment resource. With some restrictions, you can use this field to customize the Apicurio Registry Deployment. This is a Technology Preview feature.

• The Apicurio Registry Operator now sets the CORS_ALLOWED_ORIGINS environment variable, based on the value of the spec.deployment.host field. This environment variable controls the Access-Control-Allow-Origin header sent by Apicurio Registry. You can override the default value using the spec.configuration.env field.

This list may not be exhaustive. For more details, review the documentation included in the distribution archive or at Apicurio Registry documentation page (select the appropriate Apicurio Registry Operator version in the lower left corner).