Refactor YAML to Use Template Values for Security Context

[Nithinrao9696]

Summary

This PR updates the YAML configuration to replace hardcoded values for runAsUser and fsGroup with templated values. This change enhances the configurability and maintainability of the configuration files.

Details

• Updated Security Context:
  • Replaced hardcoded runAsUser value with {{ .Values.database.securityContext.runAsUser }}
  • Replaced hardcoded fsGroup value with {{ .Values.database.securityContext.fsGroup }}

These changes allow for more flexible configuration management by enabling the values to be defined dynamically based on the values provided in the Helm chart's values file.

Impact

• Configuration Flexibility: This update improves the flexibility of configuration management, allowing different values to be easily set through the Helm values file.
• Maintainability: Centralizing configuration values in the Helm values file makes future updates easier and reduces the risk of errors associated with hardcoding values.

How to Test

1. Ensure that the Helm values file (values.yaml or equivalent) contains the necessary runAsUser and fsGroup values under the database.securityContext section.
2. Deploy or render the Helm chart to verify that the YAML configuration reflects the templated values as expected.

Additional Notes

• No functional changes are expected; this is a refactoring change.
• Reviewers should verify that the templated values are correctly applied during deployment.

Please review the changes and provide feedback.

[Nithinrao9696]

@Vad1mo please check when you get a chance

[Nithinrao9696]

can someone please take appropriate action on this?

[MinerYang]

Hi @Nithinrao9696 ,

Thanks for contributing for harbor-helm, however this pod-level security contexts do not needs anymore actually, and we don't have any plan to expose this as a configuration anymore. Please kindly use the container-level security contexts.

I would like to close this PR per above comments.

Best, Miner