charts/gateway 3.0, charts/gateway-otk 2.0

[gvermeulen7205]

Description of the change

3.0.0 Updates to Hazelcast (as per PR #141)

Hazelcast 4.x/5.x servers are now supported this represents a breaking change if you have configured an external Hazelcast 3.x server.

• If you are using Gateway v10.1 and below you will either need to set hazelcast.legacy.enabled=true and use the following gateway image docker.io/caapim/gateway:10.1.00_20220802 or update your external Hazelcast server.
• The included Hazelcast subChart has been updated to reflect this change

3.0.0 Updates to Ingress Configuration

Ingress configuration has been updated to include multiple hosts, please see Ingress Configuration for more detail. You will need to update your values.yaml to reflect the changes.

3.0.0 General Updates

• You can now configure Gateway Ports. This does not cover Kubernetes Service level configuration which will need to be updated to reflect your changes.

• New Management Service

  • Provides separation of concerns for external/management traffic. This was previously a manual step.

• Autoscaling

• Ingress Configuration

• PM Tagger

  • PM (Policy Manager) tagger is a lightweight go application that works with the new management service.
  • RBAC Role Required if using PM Tagger.

• Default values.yaml restructure

  • configuration items more closely aligned

• Added production-values.yaml

  • Includes a baseline for production configuration
  • Resources are set to minimum recommended values
  • Application ports are hardened
  • 8080 (disabled)
  • 8443 (management features disabled - service is ClusterIP)
  • 9443 (configured with management service)
  • Autoscaling is enabled
  • Ingress is enabled
  • Rules are configured for 8443
  • Database is not created - you will need to supply a JDBC Url

Benefits

• New features and configuration options
• Better instruction for production scenarios
• Updated subCharts

Drawbacks

• Breaking changes to Hazelcast (documented)
• Breaking changes to default service/ingress configurations (documented)

Applicable issues

• Stable Policy Manager connection
• Gateway Application Port configuration
• Ingress Configuration

Additional information Please read the docs before attempting an upgrade of your environment. Always start with non-critical environments.

Checklist

• [X] Chart version bumped in Chart.yaml according to semver.
• [X] Variables are documented in the README.md
• [X] Title of the PR starts with chart name (e.g. [charts/gateway])
• [X] If the chart contains a values-production.yaml apart from values.yaml, ensure that you implement the changes in both files