Skip to content

Releases: IBM/operand-deployment-lifecycle-manager

v1.7.0

15 Jul 20:36
bce667c
Compare
Choose a tag to compare

For CloudPak Foundational Services v3.9.0 GA Release

v1.6.0

11 Jun 18:22
6eaa1ed
Compare
Choose a tag to compare

For CloudPak Foundational Services v3.8.0 GA Release

v1.4.3

26 Apr 22:14
75000e6
Compare
Choose a tag to compare

For Common Services v3.6.4 GA

  • Added NamespaceScope controller

v1.5.0

11 Mar 18:38
faada31
Compare
Choose a tag to compare
  • Abstract operator method with structure ODLMOperator
  • Adjust log level

v1.4.1

07 Dec 20:05
56eceec
Compare
Choose a tag to compare
  1. Support namespace scope install.
  2. Create NamespaceScope CRs.

v1.3.1

09 Oct 13:33
fe9cd5f
Compare
Choose a tag to compare
  • Refactor operator structure with Kubebuilder v2.
  • Add label operator.ibm.com/opreq-do-not-uninstall: 'true' to prevent operator uninstall.
  • ODLM can recognize the operator created by OCP console and avoid duplicate installation.

v1.2.3-durham

29 Jul 14:00
f1d3d31
Compare
Choose a tag to compare
  1. Decoupe controllers for different CRs.
  2. Remove the waiting function for the CSV creation.

v1.2.1-durham

08 Jun 20:37
87eec74
Compare
Choose a tag to compare

This is the 2020 2Q release of the operand deployment lifecycle manager.

  • Implement operator dependency management.
  • Add a new CRD OperandBindInfo to share secrets and/or configmaps with requestors

v1.1.0-cambridge

02 Apr 14:24
dd57c6e
Compare
Choose a tag to compare

This is the first release of the operand deployment lifecycle manager.

  • Implement three CRDs OperandRequest, OperandRegistry and OperandConfig.
  • OperandRequest defines which operator/operand wants to be installed in the cluster.
  • OperandRegistry defines the OLM information, like channel and catalog source, for each operator.
  • OperandConfig defines the parameters that should be used to install the operator's operand.