Description

The CRD will automatically deploy the Deployment resource and set related environment variables into the pod. However, since we're using valueFrom to set the environment variable (Ref: https://github.com/kubero-dev/kubero-operator/blob/0b6585bd2303881644ce3ffd13f4eabc053557f5/helm-charts/kubero/templates/deployment.yaml#L73-L78), Kubernetes will actually set the value to plain text instead of base64 encoded content, so we don't need to decrypt it.

Type of change

Please delete options that are not relevant.

• [x] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [ ] This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

I've built the image myself and tested it on my Kubernetes environment

Test Configuration:

• OS with version: Kubernetes 1.30.1
• Browser with version:
• SDK / CLI with version:

Checklist:

• [x] My code follows the style guidelines of this project
• [x] I have performed a self-review of my code
• [x] I documented my code, particularly in hard-to-understand areas
• [x] I have made corresponding changes to the documentation
• [x] My changes generate no new warnings
• [x] I have added tests that prove my fix is effective or that my feature works
• [x] New and existing unit tests pass locally with my changes
• [x] Any dependent changes have been merged and published in downstream modules

I finally had a closer look into it. I can't merge it for the current version since it would break older installations.

But I'll keep this open as a reminder to refactor it, in next major release.