Introduced a new field named firewall_version to granularly control the version for the firewall.
Updated the codebase to use the peer name instead of the organization name itself, enabling support for the deployment of multiple peers.
Fixed the path for correctly retrieving secrets from Vault when the firewall is enabled.
Additional changes:
Converted all the charts that were using PVC into a StatefulSet with the support of volumeClaimTemplates to resolve the volume affinity issue.
Deleted all the pvc.yaml files as they are no longer needed.
Updated templates to use the correct Kubernetes-Auth engine path for all the charts.
Updated the vault_kubernetes_job.tpl file to use the nameOverride field, allowing the allocation of a custom name based on the organization name (like <org_name>.vaultk8s-job). This change ensures the successful passing of the 20-retries check. Otherwise, assigning the default name bevel-vault-mgmt from the chart.yaml will not pass the 20-tries check, as during automated deployment using Ansible, we follow a pattern to assign names based on the component_name field.
Updated StorageClass name to <org_name>-bevel-storageclass from <org_name>-<org_cloudProvider>-storageclass, supporting a uniform naming pattern for all clouds.
Commit to be reviewed
bug(r3-corda-ent): refactor bevel r3-corda-ent codebase
Changes:
firewall_versionto granularly control the version for the firewall.Additional changes:
volumeClaimTemplatesto resolve the volume affinity issue.pvc.yamlfiles as they are no longer needed.vault_kubernetes_job.tplfile to use thenameOverridefield, allowing the allocation of a custom name based on the organization name (like<org_name>.vaultk8s-job). This change ensures the successful passing of the 20-retries check. Otherwise, assigning the default namebevel-vault-mgmtfrom thechart.yamlwill not pass the 20-tries check, as during automated deployment using Ansible, we follow a pattern to assign names based on thecomponent_namefield.StorageClassname to<org_name>-bevel-storageclassfrom<org_name>-<org_cloudProvider>-storageclass, supporting a uniform naming pattern for all clouds.fixes #2457