prep for 11.3 release

README.md

@@ -61,7 +61,7 @@ There are many valid ways to configure CI pipelines, but to help you get started
 
 Each new release of rok8s-scripts generates CI images for common workflows. These images include a set of common CI/CD dependencies, including Docker, Kubernetes, Helm, AWS, and Google Cloud client libraries. Starting with these images as a base for deployment workflows ensures that you don't need to spend any build time installing extra dependencies.
 
-We currently include CI Images based on Alpine and Debian Stretch as our recommended starting points. The latest Debian Stretch release can be pulled from `quay.io/reactiveops/ci-images:v11.2-stretch`. A full list of image tags is available on our [Quay repository](https://quay.io/repository/reactiveops/ci-images).
+We currently include CI Images based on Alpine and Debian Stretch as our recommended starting points. The latest Debian Stretch release can be pulled from `quay.io/reactiveops/ci-images:v11.3-stretch`. A full list of image tags is available on our [Quay repository](https://quay.io/repository/reactiveops/ci-images).
 
 **Deprecation Notice** As of v10 and onward, alpine and stretch will be the only available images.
 
@@ -83,7 +83,7 @@ Here is a set of guidelines to follow when deciding what version of ci-images (a
 
 You want rok8s-scripts to be stable, and just keep working until you decide to upgrade.
 
-In this scenario, you should pin to a minor version of rok8s-scripts such as `v11.2-alpine`.
+In this scenario, you should pin to a minor version of rok8s-scripts such as `v11.3-alpine`.
 
 #### You like to live dangerously
 

docs/index.md

@@ -61,7 +61,7 @@ There are many valid ways to configure CI pipelines, but to help you get started
 
 Each new release of rok8s-scripts generates CI images for common workflows. These images include a set of common CI/CD dependencies, including Docker, Kubernetes, Helm, AWS, and Google Cloud client libraries. Starting with these images as a base for deployment workflows ensures that you don't need to spend any build time installing extra dependencies.
 
-We currently include CI Images based on Alpine and Debian Stretch as our recommended starting points. The latest Debian Stretch release can be pulled from `quay.io/reactiveops/ci-images:v11.2-stretch`. A full list of image tags is available on our [Quay repository](https://quay.io/repository/reactiveops/ci-images).
+We currently include CI Images based on Alpine and Debian Stretch as our recommended starting points. The latest Debian Stretch release can be pulled from `quay.io/reactiveops/ci-images:v11.3-stretch`. A full list of image tags is available on our [Quay repository](https://quay.io/repository/reactiveops/ci-images).
 
 **Deprecation Notice** As of v10 and onward, alpine and stretch will be the only available images.
 
@@ -83,7 +83,7 @@ Here is a set of guidelines to follow when deciding what version of ci-images (a
 
 You want rok8s-scripts to be stable, and just keep working until you decide to upgrade.
 
-In this scenario, you should pin to a minor version of rok8s-scripts such as `v11.2-alpine`.
+In this scenario, you should pin to a minor version of rok8s-scripts such as `v11.3-alpine`.
 
 #### You like to live dangerously
 

examples/ci/.circleci/config.yml

@@ -14,7 +14,7 @@ references:
 
   deploy_steps: &deploy_steps
     docker:
-      - image: quay.io/reactiveops/ci-images:v11.2-alpine
+      - image: quay.io/reactiveops/ci-images:v11.3-alpine
     steps:
       - checkout
       - *set_environment_variables
@@ -24,7 +24,7 @@ references:
 jobs:
   imagebuild:
     docker:
-      - image: quay.io/reactiveops/ci-images:v11.2-alpine
+      - image: quay.io/reactiveops/ci-images:v11.3-alpine
     steps:
       - checkout
       - setup_remote_docker

examples/ci/.gitlab-ci.yml

@@ -13,7 +13,7 @@ variables:
     DOCKER_HOST: tcp://localhost:2375
     DOCKER_DRIVER: overlay2
 
-image: quay.io/reactiveops/ci-images:v11.2-alpine
+image: quay.io/reactiveops/ci-images:v11.3-alpine
 services:
   - docker:dind
 

examples/ci/bitbucket-pipelines.yml

@@ -1,4 +1,4 @@
-image: quay.io/reactiveops/ci-images:v11.2-stretch
+image: quay.io/reactiveops/ci-images:v11.3-stretch
 
 aliases:
   - &initialize-env |

examples/ephemeral-environments/.circleci/config.yml

@@ -1,7 +1,7 @@
 version: 2.1
 
 orbs:
-  rok8s-scripts: fairwinds/rok8s-scripts@11.2
+  rok8s-scripts: fairwinds/rok8s-scripts@11.3
 
 jobs:
   deploy-ephemeral:

examples/external-secrets-manager/.circleci/config.yml

@@ -21,7 +21,7 @@ references:
 jobs:
   deploy:
     docker:
-      - image: quay.io/reactiveops/ci-images:v11.2-stretch
+      - image: quay.io/reactiveops/ci-images:v11.3-stretch
     steps:
       - checkout
       - setup_remote_docker

examples/minimal-sops-secrets/.circleci/config.yml

@@ -30,15 +30,15 @@ references:
 jobs:
   build_image:
     docker:
-      - image: quay.io/reactiveops/ci-images:v11.2-stretch
+      - image: quay.io/reactiveops/ci-images:v11.3-stretch
     steps:
       - checkout
       - setup_remote_docker
       - *set_environment_variables
       - *build_image
   deploy:
     docker:
-      - image: quay.io/reactiveops/ci-images:v11.2-stretch
+      - image: quay.io/reactiveops/ci-images:v11.3-stretch
     steps:
       - checkout
       - setup_remote_docker

examples/minimal-sops-secrets/README.md

@@ -19,7 +19,7 @@ we run some of the scripts provided by rok8s-scripts. In particular, we use:
 * `k8s-deploy-and-verify` to deploy our image to Kubernetes and make sure the deployment succeeded
 	* This also calls the `k8s-deploy-secrets` script to decrypt and deploy secrets
 
-We also use the rok8s-scripts CI image, `quay.io/reactiveops/ci-images:v11.2-stretch`,
+We also use the rok8s-scripts CI image, `quay.io/reactiveops/ci-images:v11.3-stretch`,
 to ensure rok8s-scripts and its dependencies are available during the build and deploy jobs.
 
 ## Try it out

examples/minimal/.circleci/config.yml

@@ -30,15 +30,15 @@ references:
 jobs:
   build_image:
     docker:
-      - image: quay.io/reactiveops/ci-images:v11.2-stretch
+      - image: quay.io/reactiveops/ci-images:v11.3-stretch
     steps:
       - checkout
       - setup_remote_docker
       - *set_environment_variables
       - *build_image
   deploy:
     docker:
-      - image: quay.io/reactiveops/ci-images:v11.2-stretch
+      - image: quay.io/reactiveops/ci-images:v11.3-stretch
     steps:
       - checkout
       - setup_remote_docker

examples/minimal/README.md

@@ -18,7 +18,7 @@ we run some of the scripts provided by rok8s-scripts. In particular, we use:
 * `prepare-kubectl` to configure the `kubectl` command to be able to deploy resources to our Kubernetes cluster
 * `k8s-deploy-and-verify` to deploy our image to Kubernetes and make sure the deployment succeeded
 
-We also use the rok8s-scripts CI image, `quay.io/reactiveops/ci-images:v11.2-stretch`,
+We also use the rok8s-scripts CI image, `quay.io/reactiveops/ci-images:v11.3-stretch`,
 to ensure rok8s-scripts and its dependencies are available during the build and deploy jobs.
 
 ## Try it out

examples/production-ready/.circleci/config.yml

@@ -1,7 +1,7 @@
 version: 2.1
 
 orbs:
-  rok8s-scripts: fairwinds/rok8s-scripts@11.2
+  rok8s-scripts: fairwinds/rok8s-scripts@11.3
 
 jobs:
   test:

orb/executors/ci-images.yml

@@ -1,6 +1,6 @@
 parameters:
   version:
     type: string
-    default: "v11.2-stretch"
+    default: "v11.3-stretch"
 docker:
   - image: quay.io/reactiveops/ci-images:<<parameters.version>>

orb/executors/default.yml

@@ -1,6 +1,6 @@
 parameters:
   version:
     type: string
-    default: "v11.2-stretch"
+    default: "v11.3-stretch"
 docker:
   - image: quay.io/reactiveops/ci-images:<<parameters.version>>