Bump version: 1.0.0 → 1.0.1

.bumpversion.cfg

@@ -1,7 +1,7 @@
 [bumpversion]
 commit = True
 tag = True
-current_version = 1.0.0
+current_version = 1.0.1
 parse = (?P<major>\d+)\.(?P<minor>\d+)\.(?P<patch>\d+)(\-rc(?P<rc>\d+))?
 serialize = 
 	{major}.{minor}.{patch}-rc{rc}

README.md

@@ -54,15 +54,15 @@ Then, execute:
 
 ```bash
 helm repo add gpm https://sighupio.github.io/gatekeeper-policy-manager
-helm upgrade --install --namespace gatekeeper-system --set image.tag=v1.0.0 --values my-values.yaml gpm/gatekeeper-policy-manager
+helm upgrade --install --namespace gatekeeper-system --set image.tag=v1.0.1 --values my-values.yaml gpm/gatekeeper-policy-manager
 ```
 
 ## Running locally
 
 GPM can also be run locally using docker and a `kubeconfig`, assuming that the `kubeconfig` file you want to use is located at `~/.kube/config` the command to run GPM locally would be:
 
 ```bash
-docker run -v ~/.kube/config:/home/gpm/.kube/config -p 8080:8080 quay.io/sighup/gatekeeper-policy-manager:v1.0.0
+docker run -v ~/.kube/config:/home/gpm/.kube/config -p 8080:8080 quay.io/sighup/gatekeeper-policy-manager:v1.0.1
 ```
 
 Then access it with your browser on: [http://127.0.0.1:8080](http://127.0.0.1:8080)
@@ -97,7 +97,7 @@ GPM is a stateless application, but it can be configured using environment varia
 
 ### Multi-cluster support
 
-Since `v1.0.0` GPM has basic multi-cluster support when using a `kubeconfig` with more than one context. GPM will let you chose the context right from the UI.
+Since `v1.0.1` GPM has basic multi-cluster support when using a `kubeconfig` with more than one context. GPM will let you chose the context right from the UI.
 
 If you want to run GPM in a cluster but with multi-cluster support, it's as easy as mounting a `kubeconfig` file in GPM's pod(s) with the cluster access configuration and set the environment variable `KUBECONFIG` with the path to the mounted `kubeconfig` file. Or you can simply mount it in `/home/gpm/.kube/config` and GPM will detect it automatically.
 
@@ -117,7 +117,7 @@ You can customize the container image with a `Dockerfile` like the following:
 FROM curlimages/curl:7.81.0 as downloader
 RUN curl https://github.com/kubernetes-sigs/aws-iam-authenticator/releases/download/v0.5.5/aws-iam-authenticator_0.5.5_linux_amd64 --output /tmp/aws-iam-authenticator
 RUN chmod +x /tmp/aws-iam-authenticator
-FROM quay.io/sighup/gatekeeper-policy-manager:v1.0.0
+FROM quay.io/sighup/gatekeeper-policy-manager:v1.0.1
 COPY --from=downloader --chown=root:root /tmp/aws-iam-authenticator /usr/local/bin/
 ```
 

app/web-client/src/components/Footer/Component.tsx

@@ -22,7 +22,7 @@ function FooterComponent() {
         <EuiFlexItem grow={false}>
           <EuiText size="s">
             <p>
-              <strong>Gatekeeper Policy Manager v1.0.0</strong>
+              <strong>Gatekeeper Policy Manager v1.0.1</strong>
             </p>
           </EuiText>
           <EuiText size="s">

chart/Chart.yaml

@@ -24,4 +24,4 @@ version: "0.3.0"
 # This is the version number of the application being deployed. This version number should be
 # incremented each time you make changes to the application. Versions are not expected to
 # follow Semantic Versioning. They should reflect the version the application is using.
-appVersion: "v1.0.0"
+appVersion: "v1.0.1"

chart/values.yaml

@@ -8,7 +8,7 @@ image:
   repository: quay.io/sighup/gatekeeper-policy-manager
   pullPolicy: IfNotPresent
   # Overrides the image tag whose default is the chart appVersion.
-  tag: "v1.0.0"
+  tag: "v1.0.1"
 
 imagePullSecrets: []
 nameOverride: ""

kustomization.yaml

@@ -29,4 +29,4 @@ resources:
 
 images:
   - name: quay.io/sighup/gatekeeper-policy-manager
-    newTag: "v1.0.0"
+    newTag: "v1.0.1"