The goal of this user story is to make the operand POD consume its secret as volume mount for the CRs with AWS DNS provider.
This removes the sensitive data from the environment of the container and adds additional access control (DAC, MAC). Also, this enables the ability to get the updated contents of the consumed secret.

Note:

• As the Operator is already published as TechPreview in 4.10, we must keep the the contents of the secret compatible
• AWS_SHARED_CREDENTIALS_FILE environment variable can be used to set a custom path to AWS credentials file
• Cloud Credentials Operator generates a secret with a dedicated field for the contents of AWS credentials file

Acceptance Criteria

• Code and unit tests updated
• E2E tests migrated to the new format for the secret
• Markdown docs updated