Refactored the examples and rendered directories into one for better usability,

[jvoravong]

This refactor combines the rendered and example directories so they are one. Also added more examples for the most popular use cases.

• All examples will now be rendered and updated as this project grows.
• The examples are rendered in parallel.
• This will help users understand the examples without even downloading the source code and using Helm commands.
• This can help users understand the differences in each release, especially for some of our more unique Helm value configurations (especially Openshift Security Constraints).

Current Directory Structure:

splunk-otel-collector-chart % tree
.
├── examples
│   ├── README.md
│   ├── add-receiver-creator-values.yaml
│   ├── ...
│   └── use-values.yaml
├── helm-charts
├── rendered
│   ├── README.md
│   ├── manifests
│   │   ├── agent-only
│   │       ├── clusterRole.yaml
│   │       ├── clusterRoleBinding.yaml
│   │       ├── ...
│   │       └── serviceAccount.yaml
│   ├── ....
│   │   └── traces-only
│   │       ├── clusterRole.yaml
│   │       ├── clusterRoleBinding.yaml
│   │       ├── ...
│   │       └── serviceAccount.yaml
│   └── values.yaml
└── test

Refactor Directory Structure:

splunk-otel-collector-chart % tree
.
├── examples
│   ├── README.md
│   ├── add-receiver-creator
│   │   ├── README.md
│   │   ├── add-receiver-creator-values.yaml
│   │   └── rendered_manifests
│   │       ├── clusterRole.yaml
│   │       ├── clusterRoleBinding.yaml
│   │       ├── ...
│   │       └── serviceAccount.yaml
│   ├── ....
│   ├──  use-custom-gateway-values
│   │   ├── README.md
│   │   └── use-custom-gateway-values.yaml
│   │   └── rendered_manifests
│   │       ├── clusterRole.yaml
│   │       ├── clusterRoleBinding.yaml
│   │       ├── ...
│   │       └── serviceAccount.yaml
│   └── use-proxy
│       ├── README.md
│       ├── rendered_manifests
│       └── use-proxy-values.yaml
├── helm-charts
└── test

When reviewing this PR, I'd suggest only reviewing the first commit because all the new rendered yaml files are added in the second commit.

[crobert-1]

A lot of random little wording nits, sorry if it's a bit overboard! Thanks for the reorganization!

I only reviewed the first commit, as suggested.

[dmitryax]

Why it's 13k+ changeset? Do we add new examples?

[dmitryax]

Also added more examples for the most popular use cases.

Can you please do that in a follow-up PR and keep this changeset for the refactoring only?

[jvoravong]

I was having "make render" render all the examples and place the output k8s manifests into respective subdirectories, that's how this PR got up to +13k. Disabled rendering for now.

Several users keep reaching out for specific rendered Helm Chart files created from different configurations at different versions of the chart. So I would like to ease this pain point.

[dmitryax]

I was having "make render" render all the examples and place the output k8s manifests into respective subdirectories, that's how this PR got up to +13k. Disabled rendering for now.

Sorry, I still don't understand why it's such a big changeset if you didn't add any new examples. The rendered files shouldn't be changed significantly, they just moved around, right?

[dmitryax]

LGTM @crobert-1 PTAL

[jvoravong]

@crobert-1 the last commit I just added (505ece8)addresses the last of the comments you had.

I'm going to add one more commit now that will re-enable rendering and add back the large number of rendered files.

[crobert-1]

Thanks for making all of those updates!