Bump version number to 4.0.3

Author: Chris Wiechmann

README.md

@@ -155,12 +155,12 @@ Please select the Axway- or Community-Supported release. The community release a
 
 #### Community-Version
 ```
-wget --no-check-certificate https://github.com/Axway-API-Management-Plus/apigateway-openlogging-elk/releases/download/v4.0.2/axway-apim-elk-v4.0.2.tar.gz -O - | tar -xvz
+wget --no-check-certificate https://github.com/Axway-API-Management-Plus/apigateway-openlogging-elk/releases/download/v4.0.3/axway-apim-elk-v4.0.3.tar.gz -O - | tar -xvz
 ```
 
 #### Axway Supported-Version
 ```
-wget --no-check-certificate https://github.com/Axway-API-Management-Plus/apigateway-openlogging-elk/releases/download/v4.0.2/axway-apim-elk-v4.0.2.tar.gz -O - | tar -xvz
+wget --no-check-certificate https://github.com/Axway-API-Management-Plus/apigateway-openlogging-elk/releases/download/v4.0.3/axway-apim-elk-v4.0.3.tar.gz -O - | tar -xvz
 ```
 
 To simplify updates it is recommended to create a Symlink-Folder and finally rename the provided file `env-sample` to `.env`.  
@@ -1207,7 +1207,7 @@ You can find more information here: https://www.elastic.co/pricing/
 
 ### Is this solution officially supported by Axway?
 
-Yes, the solution is supported by Axway. A distinction is made between Community and Axway Supported releases, which are marked accordingly in the release directory. For example, currently version 4.0.2 is Axway supported and accordingly you can create normal Axway support cases.  
+Yes, the solution is supported by Axway. A distinction is made between Community and Axway Supported releases, which are marked accordingly in the release directory. For example, currently version 4.0.3 is Axway supported and accordingly you can create normal Axway support cases.  
 
 #### Axway Supported Release
 

UPDATE.md

@@ -66,18 +66,18 @@ On the other hand, the API builder Docker image, as a central component of the s
 
 ## Upgrade components
 
-The following example shows how to load/unpack release 4.0.2 and apply your current configuration from, for example, version 3.2.0. Regardless of which components have changed, you should install the same release package and take over your configuration on all machines to avoid confusion.  
+The following example shows how to load/unpack release 4.0.3 and apply your current configuration from, for example, version 3.2.0. Regardless of which components have changed, you should install the same release package and take over your configuration on all machines to avoid confusion.  
 
 ```
 # Perform these steps on all belonging machines
 # Get and extract the release package
-wget --no-check-certificate https://github.com/Axway-API-Management-Plus/apigateway-openlogging-elk/releases/download/v4.0.2/axway-apim-elk-v4.0.2.tar.gz -O - | tar -xvz
+wget --no-check-certificate https://github.com/Axway-API-Management-Plus/apigateway-openlogging-elk/releases/download/v4.0.3/axway-apim-elk-v4.0.3.tar.gz -O - | tar -xvz
 # The following directory has been created
-cd axway-apim-elk-v4.0.2
+cd axway-apim-elk-v4.0.3
 # Take over existing configuration from the previous version
 cp ~/axway-apim-elk-v3.2.0/.env .
 # Also copy existing certificates, scripts, extra config-files from the previous version
-cp ~/axway-apim-elk-v3.1.0/config/all-my-custom-certificates ./config
+cp ~/axway-apim-elk-v3.2.0/config/all-my-custom-certificates ./config
 ```
 
 You can then update each component as described below.
@@ -168,7 +168,7 @@ Updating the Elasticsearch cluster happens one node after next. Make sure:
 
 ```
 # On the Elasticsearch node you would like to update, navigate into your ELK-Solution directory
-cd axway-apim-elk-v4.0.2
+cd axway-apim-elk-v4.0.3
 # Stop the existing Elasticsearch container you would like to update
 docker stop elasticsearch1
 # Start a new Elasticsearch node (in this case Elasticsearch-Node-1), which will 
@@ -184,7 +184,7 @@ It is recommended to run the entire Elastic stack with the same version, so Kiba
 
 ```
 # On the Kibana node you would like to update, navigate into your ELK-Solution directory
-cd axway-apim-elk-v4.0.2
+cd axway-apim-elk-v4.0.3
 # Stop the existing Kibana container
 docker stop kibana
 # Start a new Kibana-Container with the configured ELASTIC_VERSION in your .env file
@@ -196,7 +196,7 @@ __4. Update Logstash__
 It is recommended to run the entire Elastic stack with the same version, so Logstash should/must be updated as well. Same procedure as for Kibana but repeat this on all Logstash nodes.
 ```
 # On the Logstash node you would like to update, navigate into your ELK-Solution directory
-cd axway-apim-elk-v4.0.2
+cd axway-apim-elk-v4.0.3
 # Stop the existing Logstash container
 docker stop logstash
 # Start a new Logstash with the configured ELASTIC_VERSION in your .env file
@@ -209,7 +209,7 @@ It is recommended to run the entire Elastic stack with the same version, so File
 
 ```
 # On the Filebeat node you would like to update, navigate into your ELK-Solution directory
-cd axway-apim-elk-v4.0.2
+cd axway-apim-elk-v4.0.3
 # Stop existing filebeat container
 docker stop filebeat
 # Start a new Filebeat with the configured ELASTIC_VERSION in your .env file

apibuilder4elastic/package.json

@@ -2,7 +2,7 @@
 	"name": "apibuilder4elastic",
 	"description": "This API-Builder project provides an ELK-Based Traffic-Monitor API.",
 	"main": "app.js",
-	"version": "v4.0.2",
+	"version": "v4.0.3",
 	"author": "Chris Wiechmann",
 	"email": "cwiechmann@axway.com",
 	"url": "https://axway.com",

docker-compose.yml

@@ -57,7 +57,7 @@ services:
 
   # This is the API-Builder project exposing the API-Gateway Manager REST-API
   apibuilder4elastic:
-    image: cwiechmann/apibuilder4elastic:v4.0.2
+    image: cwiechmann/apibuilder4elastic:v4.0.3
     restart: on-failure:10
     container_name: apibuilder4elastic
     environment:

helm/Chart.yaml

@@ -4,9 +4,9 @@ description: A Helm chart for the Axway APIM Elasticsearch integration.
 
 type: application
 
-version: 4.0.2
+version: 4.0.3
 
-appVersion: "4.0.2"
+appVersion: "4.0.3"
 
 dependencies:
   - name: logstash

helm/README.md

@@ -85,7 +85,7 @@ kubectl apply -n apim-elk -f https://raw.githubusercontent.com/Axway-API-Managem
 
 With Elasticsearch volumes and your `myvalues.yaml` file in place, you can start the installation:  
 ```
-helm install -n apim-elk -f myvalues.yaml axway-elk https://github.com/Axway-API-Management-Plus/apigateway-openlogging-elk/releases/download/v4.0.2/helm-chart-apim4elastic-v4.0.2.tgz
+helm install -n apim-elk -f myvalues.yaml axway-elk https://github.com/Axway-API-Management-Plus/apigateway-openlogging-elk/releases/download/v4.0.3/helm-chart-apim4elastic-v4.0.3.tgz
 ```
 👉 __Please note:__ The Helm Release-Name: __axway-elk__ is mandatory. Read [here](#why-helm-release-name-axway-elk) why.  
 
@@ -94,7 +94,7 @@ You may run the following commands to check the status of the deployment, pods,
 // Check the installed release
 helm list -n apim-elk
 NAME            NAMESPACE       REVISION        UPDATED                                 STATUS          CHART                           APP VERSION   
-axway-elk       apim-elk        1               2021-05-03 14:22:08.9325287 +0200 CEST  deployed        apim4elastic-4.0.2              4.0.2
+axway-elk       apim-elk        1               2021-05-03 14:22:08.9325287 +0200 CEST  deployed        apim4elastic-4.0.3              4.0.3
 
 // Check the pods, with Elasticsearch and Kibana enabled
 kubectl get pods -n apim-elk
@@ -542,7 +542,7 @@ Watch this video to see a demonstration how to update the Elastic-Stack on Kuber
 
 Example how to upgrade an existing release:  
 ```
-helm upgrade -n apim-elk -f myvalues.yaml axway-elk https://github.com/Axway-API-Management-Plus/apigateway-openlogging-elk/releases/download/v4.0.2/helm-chart-apim4elastic-v4.0.2.tgz
+helm upgrade -n apim-elk -f myvalues.yaml axway-elk https://github.com/Axway-API-Management-Plus/apigateway-openlogging-elk/releases/download/v4.0.3/helm-chart-apim4elastic-v4.0.3.tgz
 ```
 
 ## Required resources

helm/values.yaml

@@ -25,7 +25,7 @@ apibuilder4elastic:
   # Enables the APIBuilder4Elastic, which is required for the solution to work. So very unlikely to disable
   enabled: true
   image: "cwiechmann/apibuilder4elastic"
-  imageTag: "v4.0.2"
+  imageTag: "v4.0.3"
   imagePullPolicy: IfNotPresent
   nameOverride: "apibuilder4leastic"
   fullnameOverride: "Axway API-Builder4Elastic"