You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our docker images currently have a hard coded label RELEASE=1 which was required for Openshift certification. Another label is VERSION which currently is set from the product version (e.g. 3.8.0 for a ZooKeeper 3.8.0).
For RELEASE we want to update to our actual naming of our releases. The next one would be 22.09. This should probably be parameterized in the build script instead of each product image.
The version label does not make sense currently. It will always be 3.8.0 (for a ZooKeeper 3.8.0) even if we adapt, add to or change that image.
The VERSION label should become the full tag we create from that image like zookeeper3.8.0-stackable0.1.0 to clearly identify the image.
This is done when:
The RELEASE label is set "globally" via a CLI parameter in the build script
The VERSION label is set to the actually name of the created docker images like zookeeper3.8.0-stackable0.1.0
The text was updated successfully, but these errors were encountered:
Our docker images currently have a hard coded label
RELEASE=1
which was required for Openshift certification. Another label isVERSION
which currently is set from the product version (e.g. 3.8.0 for a ZooKeeper 3.8.0).For
RELEASE
we want to update to our actual naming of our releases. The next one would be22.09
. This should probably be parameterized in the build script instead of each product image.The version label does not make sense currently. It will always be 3.8.0 (for a ZooKeeper 3.8.0) even if we adapt, add to or change that image.
The
VERSION
label should become the full tag we create from that image likezookeeper3.8.0-stackable0.1.0
to clearly identify the image.This is done when:
RELEASE
label is set "globally" via a CLI parameter in the build scriptVERSION
label is set to the actually name of the created docker images likezookeeper3.8.0-stackable0.1.0
The text was updated successfully, but these errors were encountered: