Support getting aws credentials from existing secret instead of clear text in values file

[dennispan]

Description

The changes add support in the Helm chart to use an existing secret for AWS credentials, instead of having the secrets as clear texts in values file

Fixes #(issue)

How Has This Been Tested?

Tested with

helm template liqo deployments/liqo --version HEAD -f <values-file-path> --namespace liqo

[adamjensenbot]

Hi @dennispan. Thanks for your PR!

I am @adamjensenbot.
You can interact with me issuing a slash command in the first line of a comment.
Currently, I understand the following commands:

• /rebase: Rebase this PR onto the master branch (You can add the option test=true to launch the tests
  when the rebase operation is completed)
• /merge: Merge this PR into the master branch
• /build Build Liqo components
• /test Launch the E2E and Unit tests
• /hold, /unhold Add/remove the hold label to prevent merging with /merge

Make sure this PR appears in the liqo changelog, adding one of the following labels:

• kind/breaking: 💥 Breaking Change
• kind/feature: 🚀 New Feature
• kind/bug: 🐛 Bug Fix
• kind/cleanup: 🧹 Code Refactoring
• kind/docs: 📝 Documentation

[dennispan]

@aleoli Thanks for taking an initial look. Do you mind taking another look?

[aleoli]

/test

[aleoli]

Thanks @dennispan! It looks good to me!

[aleoli]

/rebase test=true

[aleoli]

Noticed now, can you please squash your commits to one?

[dennispan]

@aleoli Thank you! I've squashed and rebased the commits. BTW, what is the release process of the helm charts?

[aleoli]

/rebase test=true

[aleoli]

The helm charts are released with the liqo releases.
If you want to use a not-yet-released helm chart you can install it by using the local-chart-path flag of liqoctl.

[aleoli]

/merge