Adding RBAС for GC implementation, changing the deployment type of Ignite

Siarhei Poliak [EPAM / GCP]requested to merge
cherry-pick-da841b3c into release/0.28

Original MR: !345 (merged)

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?

  • [NO]

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?

  1. When deploying the gcz, the rbac for service accounts was missing and its use was not automated.
  2. Ignite used deployment, with the creation of PV, and when increasing the replicas, manual creation of new PVs was required.
  3. The size of the PV disk used hardcode and could not be easily changed

What is the new/expected behavior?

  1. Rbac for service accounts is created automatically during installation
  2. Ignite is deployed as a statefulset and is easily scalable, no manual creation of pv/pvc
  3. The disk size is defined in values ​​and when installing ignite is templated

Have you added/updated Unit Tests and Integration Tests?

NO

Any other useful information

all changes affect only google implementation and do not affect other providers

Edited by Marc Burnie [AWS]

Merge request reports