[
https://issues.apache.org/jira/browse/RANGER-5022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Kumar updated RANGER-5022:
-----------------------------------
Description:
Starting with ranger-usersync, I propose to collate all configs for the
usersync service and make it compatible with Helm.
This has multiple advantages:
# To enable the application to be deployed on Kubernetes effectively.
# Keeping default config values in values.yaml allows application to run with
custom configs with ease. This is effective in deploying services in various
environments (dev, test, prod).
# Helm templates allow dynamic and reusable configurations.
# Centralized parametrization with values.yaml and centralized updates to
configs with the help of templates.
# To package configs as a helm chart for distribution.
# Benefits that come with using helm.
As part of these changes, I propose to deprecate the usage of XML files
altogether, restructure the installation of the service to remove hardcoded
configs and comply with helm. This would also require changes to application
code which relies on XML libraries to read configs.
For ranger upgrades, there needs to be provision for a utility script which
would transform existing usersync configurations in XML and map it to YAML
before usersync restarts.
was:
Starting with ranger-usersync, I propose to collate all configs for the
usersync service and make it compatible with Helm.
This has multiple advantages:
# To enable the application to be deployed on Kubernetes effectively.
# Keeping default config values in values.yaml allows application to run with
custom configs with ease. This is effective in deploying services in various
environments (dev, test, prod).
# Helm templates allow dynamic and reusable configurations.
# Centralized parametrization with values.yaml and centralized updates to
configs with the help of templates.
# To package configs as a helm chart for distribution.
# Benefits that come with using helm.
As part of these changes, I propose to deprecate the usage of XML files
altogether, restructure the installtion of the service to remove hardcoded
configs and comply with helm. This would also require changes to application
code which relies on XML libraries to read configs.
> Ranger Usersync Configs to be Helm Compatible
> ---------------------------------------------
>
> Key: RANGER-5022
> URL: https://issues.apache.org/jira/browse/RANGER-5022
> Project: Ranger
> Issue Type: Improvement
> Components: Ranger
> Reporter: Abhishek Kumar
> Assignee: Abhishek Kumar
> Priority: Major
> Fix For: 3.0.0
>
>
> Starting with ranger-usersync, I propose to collate all configs for the
> usersync service and make it compatible with Helm.
> This has multiple advantages:
> # To enable the application to be deployed on Kubernetes effectively.
> # Keeping default config values in values.yaml allows application to run
> with custom configs with ease. This is effective in deploying services in
> various environments (dev, test, prod).
> # Helm templates allow dynamic and reusable configurations.
> # Centralized parametrization with values.yaml and centralized updates to
> configs with the help of templates.
> # To package configs as a helm chart for distribution.
> # Benefits that come with using helm.
>
> As part of these changes, I propose to deprecate the usage of XML files
> altogether, restructure the installation of the service to remove hardcoded
> configs and comply with helm. This would also require changes to application
> code which relies on XML libraries to read configs.
> For ranger upgrades, there needs to be provision for a utility script which
> would transform existing usersync configurations in XML and map it to YAML
> before usersync restarts.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
