CMK release - version v1.2.0-rc1.

Author: Michał Stachowski

Makefile

@@ -16,7 +16,7 @@
 
 all: docker
 
-version=v1.1.0
+version=v1.2.0-rc1
 
 # TODO: This target should be changed, when e2e tests will be ready and test
 # entrypoint will be defined.

README.md

@@ -69,7 +69,7 @@ Options:
   --cmk-cmd-list=<list> Comma seperated list of CMK sub-commands to run on
                         each host
                         [default: init,reconcile,install,discover,nodereport].
-  --cmk-img=<img>       CMK Docker image [default: cmk:v1.1.0].
+  --cmk-img=<img>       CMK Docker image [default: cmk:v1.2.0-rc1].
   --cmk-img-pol=<pol>   Image pull policy for the CMK Docker image
                         [default: IfNotPresent].
   --conf-dir=<dir>      CMK configuration directory [default: /etc/cmk].

RELEASE.md

@@ -118,21 +118,21 @@ Running Vagrant locally syncs your repository directory into `/cmk` using by def
  - check whether current branch is `master` and if it's "clean"
  - fetch origin
  - check whether `CMK_RELEASE_VER` is set, follows proper pattern and there in no existing tag with it's value
- - check whether there is no `cmk-release-v1.1.0` branch neither locally nor remotely
- - get previous version string from `Makefile` (`version=v1.1.0`) and check
+ - check whether there is no `cmk-release-v1.2.0-rc1` branch neither locally nor remotely
+ - get previous version string from `Makefile` (`version=v1.2.0-rc1`) and check
 
 If all above checks pass, script will:
- - create local branch `cmk-release-v1.1.0`
- - replace old release string (`v1.1.0`) with new one (`v1.1.0`) in all repo files
- - commit changes with message `CMK release - version v1.1.0.`
+ - create local branch `cmk-release-v1.2.0-rc1`
+ - replace old release string (`v1.2.0-rc1`) with new one (`v1.2.0-rc1`) in all repo files
+ - commit changes with message `CMK release - version v1.2.0-rc1.`
  - push branch to origin
  - checkout to `master` branch.
 
 **What will happen after PR gets to `master` branch**
 After PR is "Rebased and merged" into `master` branch, Jenkins CI/CD will start VM based on `.release/Vagrantfile` and execute `.release/make_release.py` inside the VM.
 
 **What will `make_release.py` do :**
-- check latest commit message for `CMK release - version v1.1.0.` string
-- `v1.1.0` will become tag value
+- check latest commit message for `CMK release - version v1.2.0-rc1.` string
+- `v1.2.0-rc1` will become tag value
 - generate change log
 - create release with change log based on tag found in commit message

cmk.py

@@ -44,7 +44,7 @@
   --cmk-cmd-list=<list> Comma seperated list of CMK sub-commands to run on
                         each host
                         [default: init,reconcile,install,discover,nodereport].
-  --cmk-img=<img>       CMK Docker image [default: cmk:v1.1.0].
+  --cmk-img=<img>       CMK Docker image [default: cmk:v1.2.0-rc1].
   --cmk-img-pol=<pol>   Image pull policy for the CMK Docker image
                         [default: IfNotPresent].
   --conf-dir=<dir>      CMK configuration directory [default: /etc/cmk].
@@ -85,7 +85,7 @@
 def main():
     setup_logging()
 
-    args = docopt(__doc__, version="CMK v1.1.0")
+    args = docopt(__doc__, version="CMK v1.2.0-rc1")
     if args["cluster-init"]:
         clusterinit.cluster_init(args["--host-list"], args["--all-hosts"],
                                  args["--cmk-cmd-list"], args["--cmk-img"],

docs/cli.md

@@ -49,7 +49,7 @@ Options:
   --cmk-cmd-list=<list> Comma seperated list of CMK sub-commands to run on
                         each host
                         [default: init,reconcile,install,discover,nodereport].
-  --cmk-img=<img>       CMK Docker image [default: cmk:v1.1.0].
+  --cmk-img=<img>       CMK Docker image [default: cmk:v1.2.0-rc1].
   --cmk-img-pol=<pol>   Image pull policy for the CMK Docker image
                         [default: IfNotPresent].
   --conf-dir=<dir>      CMK configuration directory [default: /etc/cmk].

docs/html/docs/cli.html

@@ -88,7 +88,7 @@ <h2>
   --cmk-cmd-list=&lt;list&gt; Comma seperated list of CMK sub-commands to run on
                         each host
                         [default: init,reconcile,install,discover,nodereport].
-  --cmk-img=&lt;img&gt;       CMK Docker image [default: cmk:v1.1.0].
+  --cmk-img=&lt;img&gt;       CMK Docker image [default: cmk:v1.2.0-rc1].
   --cmk-img-pol=&lt;pol&gt;   Image pull policy for the CMK Docker image
                         [default: IfNotPresent].
   --conf-dir=&lt;dir&gt;      CMK configuration directory [default: /etc/cmk].

docs/html/docs/operator.html

@@ -187,7 +187,7 @@ <h3>
 <li>The subcommands described below should be run in the same order.</li>
 <li>The documentation in this section assumes that the <code>CMK</code> configuration directory is <code>/etc/cmk</code> and the <code>cmk</code>
 binary is installed on the host under <code>/opt/bin</code>.</li>
-<li>In all the pod templates used in this section, the name of container image used is <code>cmk:v1.1.0</code>. It is expected that the
+<li>In all the pod templates used in this section, the name of container image used is <code>cmk:v1.2.0-rc1</code>. It is expected that the
 <code>cmk</code> container image is built and cached locally in the host. The <code>image</code> field will require modification if the
 container image is hosted remotely (e.g., in <a href="https://hub.docker.com/">https://hub.docker.com/</a>).</li>
 </ul>

docs/html/index.html

@@ -127,7 +127,7 @@ <h2>
   --cmk-cmd-list=&lt;list&gt; Comma seperated list of CMK sub-commands to run on
                         each host
                         [default: init,reconcile,install,discover,nodereport].
-  --cmk-img=&lt;img&gt;       CMK Docker image [default: cmk:v1.1.0].
+  --cmk-img=&lt;img&gt;       CMK Docker image [default: cmk:v1.2.0-rc1].
   --cmk-img-pol=&lt;pol&gt;   Image pull policy for the CMK Docker image
                         [default: IfNotPresent].
   --conf-dir=&lt;dir&gt;      CMK configuration directory [default: /etc/cmk].

docs/operator.md

@@ -125,7 +125,7 @@ for some reason.
 - The subcommands described below should be run in the same order.
 - The documentation in this section assumes that the `CMK` configuration directory is `/etc/cmk` and the `cmk`
 binary is installed on the host under `/opt/bin`.
-- In all the pod templates used in this section, the name of container image used is `cmk:v1.1.0`. It is expected that the
+- In all the pod templates used in this section, the name of container image used is `cmk:v1.2.0-rc1`. It is expected that the
 `cmk` container image is built and cached locally in the host. The `image` field will require modification if the
 container image is hosted remotely (e.g., in https://hub.docker.com/).
 

resources/pods/cmk-cluster-init-pod.yaml

@@ -27,6 +27,6 @@ spec:
     command:
     - "/bin/bash"
     - "-c"
-    image: cmk:v1.1.0
+    image: cmk:v1.2.0-rc1
     name: cmk-cluster-init-pod
   restartPolicy: Never