TDB-19508: Helm Charts for Terracotta 12.x

README.md

@@ -24,6 +24,7 @@ webmethods/terracottabigmemorymax       1.4.0           4.4.0           Terracot
 webmethods/terracottabigmemorymax       2.1.1           4.5.0           Terracotta BigMemory Max Helm Chart for Kubernetes
 webmethods/terracotta                   1.0.0           < 11.1.0.12     Terracotta Helm Chart for Kubernetes
 webmethods/terracotta                   2.0.0           >= 11.1.0.12    Terracotta Helm Chart for Kubernetes
+webmethods/terracotta                   3.0.0           12.x            Terracotta Helm Chart for Kubernetes
 webmethods/universalmessaging           1.1.0           10.15           Universal Messaging (UM) Helm Chart for Kubernetes
 ```
 

terracotta/helm/Chart.yaml

@@ -33,12 +33,12 @@ type: application
 # This is the chart version. This version number should be incremented each time you make changes
 # to the chart and its templates, including the app version.
 # Versions are expected to follow Semantic Versioning (https://semver.org/)
-version: "2.0.0"
+version: "3.0.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: "11.1"
+appVersion: "12.0"
 
 dependencies:
   - name: common

terracotta/helm/README.md

@@ -30,6 +30,7 @@ This Helm chart deploys a Terracotta cluster on Kubernetes, including:
 1. **Terracotta Server** - Distributed in-memory data management
 2. **Terracotta Management Server (TMS)** - Cluster monitoring and management
 3. **Terracotta Operator** - Manages cluster lifecycle, activation, and scaling operations
+4. Terracotta REST Gateway (optional)
 
 The chart automatically deploys the Terracotta Operator CRD during installation if not already present. Note that `helm uninstall` does not remove the CRD from the cluster.
 
@@ -60,17 +61,21 @@ invalidated._
 |---------|---------------------------------------|
 | `1.0.0' | Initial release                       |
 | `2.0.0' | Support for release name in resources |
+| `3.0.0' | Updated folder path (XPC)             |
 
 ⚠️ Resources and resources names have been updated from version 1 to version to so doing a helm uninstall/install with
 new version 2 from version 1 will not re-use the previous PVC (data). You may need to perform a manual sync of the PVC
 data.
 
+⚠️ Internal folder names in docker images have been updated in version 3.
+
 ## Compatibility Matrix
 
 | NAME                  | CHART VERSION |  APP VERSION   |
 | :-------------------- |:-------------:|:--------------:|
 | webmethods/terracotta |     `1.x`     | `<  11.1.0.12` |
 | webmethods/terracotta |     `2.x`     | `>= 11.1.0.12` |
+| webmethods/terracotta |     `3.x`     | `12.x`         |
 
 ## Prerequisites
 
@@ -480,7 +485,7 @@ This chart can also be used to run secure Terracotta cluster and TMS.
    tms.properties file must have following properties configured like following -
 
    # tms directory should be configured like following
-   tms.security.root.directory=/opt/softwareag/config/tms
+   tms.security.root.directory=/opt/terracotta/config/tms
 
    # if audit directory is required
    tms.security.audit.directory=
@@ -489,7 +494,7 @@ This chart can also be used to run secure Terracotta cluster and TMS.
    tms.security.https.enabled=true
 
    # client directory should be configured like following
-   tms.security.root.directory.connection.default=/opt/softwareag/config/client
+   tms.security.root.directory.connection.default=/opt/terracotta/config/client
    ```
 
    Next create a tar.gz for security folder like following -
@@ -537,13 +542,14 @@ Note - There are two ways in which node identity certificates can be configured.
 | securityContext.runAsNonRoot | bool | `true` |  |
 | securityContext.runAsUser | int | `1724` |  |
 | storageClass | string | `""` |  |
-| tag | float | `11.1` | Specific version to not accidentally change production versions with newer images. |
+| tag | float | `12` | Specific version to not accidentally change production versions with newer images. |
 | terracotta.affinity | string | `nil` | Configure pod affinity for terracotta server |
 | terracotta.clusterName | string | `"my-cluster"` |  |
 | terracotta.datadirs | string | `"dataroot-1,dataroot-2"` |  |
 | terracotta.failoverPriority | string | `"availability"` |  |
 | terracotta.jsonAuditLogging | bool | `true` |  |
 | terracotta.jsonLogging | bool | `false` |  |
+| terracotta.jsonSecurityLogging | bool | `true` |  |
 | terracotta.nodes | int | `2` |  |
 | terracotta.offheaps | string | `"offheap-1:512MB"` |  |
 | terracotta.probeFailureThreshold | string | `nil` |  |
@@ -566,7 +572,12 @@ Note - There are two ways in which node identity certificates can be configured.
 | tms.affinity | string | `nil` | Configure pod affinity for tms server |
 | tms.jsonAuditLogging | bool | `true` |  |
 | tms.jsonLogging | bool | `false` |  |
+| tms.jsonSecurityLogging | bool | `true` |  |
 | tms.resources | object | `{}` |  |
 | tms.storage | string | `"5Gi"` |  |
 | tms.tmsImage | string | `"ibmwebmethods.azurecr.io/terracotta-management-server"` |  |
 | tms.topologySpreadConstraints | string | `nil` | Configure pod topologySpreadConstraints for tms server |
+| trg.jsonAuditLogging | bool | `true` |  |
+| trg.jsonLogging | bool | `false` |  |
+| trg.jsonSecurityLogging | bool | `true` |  |
+| trg.trgImage | string | `"ibmwebmethods.azurecr.io/terracotta-rest-gateway"` |  |

terracotta/helm/README.md.gotmpl

@@ -30,6 +30,7 @@ This Helm chart deploys a Terracotta cluster on Kubernetes, including:
 1. **Terracotta Server** - Distributed in-memory data management
 2. **Terracotta Management Server (TMS)** - Cluster monitoring and management
 3. **Terracotta Operator** - Manages cluster lifecycle, activation, and scaling operations
+4. Terracotta REST Gateway (optional)
 
 The chart automatically deploys the Terracotta Operator CRD during installation if not already present. Note that `helm uninstall` does not remove the CRD from the cluster.
 
@@ -60,17 +61,21 @@ invalidated._
 |---------|---------------------------------------|
 | `1.0.0' | Initial release                       |
 | `2.0.0' | Support for release name in resources |
+| `3.0.0' | Updated folder path (XPC)             |
 
 ⚠️ Resources and resources names have been updated from version 1 to version to so doing a helm uninstall/install with
 new version 2 from version 1 will not re-use the previous PVC (data). You may need to perform a manual sync of the PVC
 data.
 
+⚠️ Internal folder names in docker images have been updated in version 3.
+
 ## Compatibility Matrix
 
 | NAME                  | CHART VERSION |  APP VERSION   |
 | :-------------------- |:-------------:|:--------------:|
 | webmethods/terracotta |     `1.x`     | `<  11.1.0.12` |
 | webmethods/terracotta |     `2.x`     | `>= 11.1.0.12` |
+| webmethods/terracotta |     `3.x`     | `12.x`         |
 
 ## Prerequisites
 
@@ -480,7 +485,7 @@ This chart can also be used to run secure Terracotta cluster and TMS.
    tms.properties file must have following properties configured like following -
 
    # tms directory should be configured like following
-   tms.security.root.directory=/opt/softwareag/config/tms
+   tms.security.root.directory=/opt/terracotta/config/tms
 
    # if audit directory is required
    tms.security.audit.directory=
@@ -489,7 +494,7 @@ This chart can also be used to run secure Terracotta cluster and TMS.
    tms.security.https.enabled=true
 
    # client directory should be configured like following
-   tms.security.root.directory.connection.default=/opt/softwareag/config/client
+   tms.security.root.directory.connection.default=/opt/terracotta/config/client
    ```
 
    Next create a tar.gz for security folder like following -