Skip to content
This repository has been archived by the owner on Aug 2, 2023. It is now read-only.

0.5.0-rc.1

Pre-release
Pre-release
Compare
Choose a tag to compare
@kaczyns kaczyns released this 13 Jan 16:13
5f3cc42

This is the first release candidate for the Kabanero Operator 0.5.0 release. New features:

  • The Collection CRD has been changed to support multiple versions of a collection. It is now possible to have multiple versions of the same collection active at the same time. To achieve this, list multiple Collection repositories in your Kabanero CR instance.
  • The versions of several Tekton components has changed. Pipelines is now at v0.8.0. Dashboard is now at v0.3.0. Tekton Triggers v0.1.0 is included. If you have generated Github webhooks for your pipelines using the Tekton Dashboard, they will need to be regenerated, as the Dashboard now uses Triggers to drive the pipelines.
  • The install script requires you to set the variable openshift_master_default_subdomain to the master default subdomain for your OpenShift cluster. The Tekton Dashboard may not function correctly if this variable is not set.
  • The operator now uses operator-sdk v0.11.0
  • Knative Eventing is no longer strictly required. The Kabanero install script will continue to install it, but this will be removed in a future release.

The following was used to test this release:

  • OpenShift Container Platform (OCP) 4.2
  • OpenShift Service Mesh 1.0.2
  • OpenShift Serverless Operator 1.2.0
  • OpenShift Pipelines Operator 0.8.1
  • Knative Eventing Operator 0.9
  • Knative Sources 0.9
  • Appsody Operator 0.3.0
  • Eclipse Che Operator 7.3.1

Deprecation note - It is our intention to release a set of v1alpha2 CRDs in the next release. It is also our intention to deprecate the v1alpha1 CRDs in that release, to be removed in 3-6 months time. Specifically, the singleton version, desiredState and repositoryUrl fields on the Collection CRD will be removed in v1alpha2, and are replaced by the new versions array introduced in v1alpha1. Users consuming Kabanero releases in order will not need to perform any migration.

This is a release-candidate and is not intended for production use. Our intention is to delete the release and its associated containers in 90 days.