Issue #42: Tag new 0.3.0 release.

README.md

@@ -154,11 +154,11 @@ Each of these must be appropriately built in preparation for a new tag:
 
 Run the following command inside this directory:
 
-    operator-sdk build geerlingguy/tower-operator:0.2.6
+    operator-sdk build geerlingguy/tower-operator:0.3.0
 
 Then push the generated image to Docker Hub:
 
-    docker push geerlingguy/tower-operator:0.2.6
+    docker push geerlingguy/tower-operator:0.3.0
 
 #### Build a new version of the `tower-operator.yaml` file
 

build/chain-operator-files.yml

@@ -6,7 +6,7 @@
   gather_facts: false
 
   vars:
-    operator_image: geerlingguy/tower-operator:0.2.6
+    operator_image: geerlingguy/tower-operator:0.3.0
     pull_policy: Always
     operator_file_path: "../deploy/tower-operator.yaml"
     operator_template: "../deploy/operator.yaml"

deploy/tower-operator.yaml

@@ -113,14 +113,14 @@ spec:
             - /usr/local/bin/ao-logs
             - /tmp/ansible-operator/runner
             - stdout
-          image: "geerlingguy/tower-operator:0.2.6"
+          image: "geerlingguy/tower-operator:0.3.0"
           imagePullPolicy: "Always"
           volumeMounts:
             - mountPath: /tmp/ansible-operator/runner
               name: runner
               readOnly: true
         - name: operator
-          image: "geerlingguy/tower-operator:0.2.6"
+          image: "geerlingguy/tower-operator:0.3.0"
           imagePullPolicy: "Always"
           volumeMounts:
             - mountPath: /tmp/ansible-operator/runner