[Azure] gcz chart fix and enhancement
Type of change
-
Bug Fix -
Feature
Please provide link to gitlab issue or ADR(Architecture Decision Record)
Does this introduce a change in the core logic?
- [YES]
Does this introduce a change in the cloud provider implementation, if so which cloud?
-
AWS -
Azure -
GCP -
IBM
Does this introduce a breaking change?
- [NO]
What is the current behavior?
- Classpath it is not needed as the file will be validated afterwards more info here, removing that validation as it cannot use files while running in container with
java -jar
- Add new property to be able to setup dynamically through helm templates the location of the
koop-config.json
, allowing flexibility for devops to set a variable value. - Helm chart for azure are not working properly.
- Persistence it is not enabled for gridgain, therefore all changes are wiped out in azure implementation.
- Current implementation it is incompatible with istio
What is the new/expected behavior?
- Persistent configuration stored in DB
- Allow devops to use any file for bootstrap initialization of provider
- Enabled istio compatibility to use in the same cluster as the one which it is used by core-services in azure implementation
Have you added/updated Unit Tests and Integration Tests?
NO
Any other useful information
Switched to oficial gridgain/ignite helm charts for simplicity, this will reduce the helm template workload burden.