feat: include cluster-autoscaler and move chart configurations

[marbonilla]

This PR introduces two main changes:

1. Cluster Autoscaler Installation:
   The chart for deploying cluster-autoscaler is added, along with its proposed configuration in values-example.yaml.

2. Configuration Reorganization in values.yaml:
   The values.yaml file has been cleaned up to include only the minimum required configuration, making it fully customizable for different needs. The previously defined configuration values have been moved to values-example.yaml. This change addresses issues caused by configuration overrides in the values.

CC @jfavellar90

[openedx-webhooks]

Thanks for the pull request, @marbonilla!

This repository is currently maintained by @openedx/openedx-k8s-harmony-maintainers.

Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review.

🔘 Get product approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

• If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
  • This process (including the steps you'll need to take) is documented here.
• If it doesn't, simply proceed with the next step.

🔘 Provide context

To help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:

• Dependencies

  This PR must be merged before / after / at the same time as ...

• Blockers

  This PR is waiting for OEP-1234 to be accepted.

• Timeline information

  This PR must be merged by XX date because ...

• Partner information

  This is for a course on edx.org.

• Supporting documentation
• Relevant Open edX discussion forum threads

🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

---

Where can I find more information?

If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:

• Overview of Review Process for Community Contributions
• Pull Request Status Guide
• Making changes to your pull request

When can I expect my changes to be merged?

Our goal is to get community contributions seen and reviewed as efficiently as possible.

However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:

• The size and impact of the changes that it introduces
• The need for product review
• Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.

[itsjeyd]

Hey @marbonilla, thank you for this contribution!

The next step will be for you to submit a signed CLA. For details see Submit a signed contributor agreement (CLA) in the bot's comment above.

[itsjeyd]

@marbonilla Friendly reminder to follow up on the previous comment ⬆️

[itsjeyd]

Hey @marbonilla, just checking in to see if you're still planning to continue working on this PR?

[marbonilla]

@openedx/cla-problems
Hi,
I've already signed the necessary documents, but I can't get through the CLA check.
I'm very grateful for your help.

[itsjeyd]

@marbonilla Looks like the CLA check passed 🎉

Aside from resolving branch conflicts ⬆️, are you planning to make more changes to the code? If not, we can line this PR up for a test run; let me know.

[marbonilla]

let me know

Hi @itsjeyd, there will be no additional changes for now

[itsjeyd]

Thanks @marbonilla.

@openedx/openedx-k8s-harmony-maintainers Could you please kick off a build for this PR?

[itsjeyd]

@openedx/openedx-k8s-harmony-maintainers

Could you please kick off a build for this PR?

A friendly ping on this ⬆️

[itsjeyd]

Hi @openedx/committers-openedx-k8s-harmony, this PR is ready for review now.

[gabor-boros]

I understand the reasoning behind removing the pretty verbose sink configuration, but I believe it should be kept around. For those who are configuring this for the first time, this sink configuration can be relatively complex and would help them to get started.

If we don't want to "pollute" the value examples, then we can create a docs directory in the repo with a README for configuring the sinks and reference that from the value examples. If there is an existing documentation with an example elsewhere, it could be linked instead of creating docs on our own.