feat: Updated SS and microservices deployment docs

[Jayclifford345]

This PR updates our helm documentation inline with our 3.0 deployment for:

• Simple Scalable
• Microservices

Checklist

• Reviewed the CONTRIBUTING.md guide (required)
• Documentation added
• Tests updated
• Title matches the required conventional commits format, see here
  • Note that Promtail is considered to be feature complete, and future development for logs collection will be in Grafana Alloy. As such, feat PRs are unlikely to be accepted unless a case can be made for the feature actually being a bug fix to existing behavior.
• Changes that require user attention or interaction to upgrade are documented in docs/sources/setup/upgrade/_index.md
• For Helm chart changes bump the Helm chart version in production/helm/loki/Chart.yaml and update production/helm/loki/CHANGELOG.md and production/helm/loki/README.md. Example PR
• If the change is deprecating or removing a configuration option, update the deprecated-config.yaml and deleted-config.yaml files respectively in the tools/deprecated-config-checker directory. Example PR

[JStickler]

[docs team]

[JStickler]

FYI - It has been released, just not publicized yet.

https://github.com/grafana/meta-monitoring-chart/releases

[Jayclifford345]

This is really cool!! I noticed we had a monitoring and alerting section in deployments. I have linked to that for now. I can create a new PR with updated instructions for that section of the docs with the repo instructions

[JStickler]

Not exactly sure if we need this topic, since we don't have a "testing" topic for the other installation methods. I would assume that customers would test in a test environment before installing on a production environment. Have you seen different behavior?

[Jayclifford345]

So I have changed the name slightly to help. Essentially I wanted to provide our community with an easy to step by step guide on how to practise deploying this locally just so they can understand how the helm deploys without needing to set up a full cloud k8's stack. It mostly helped me as I was testing the new deployment helms that the team created :). But happy to remove if its overkill as might also be confusing

[JStickler]

After you explained in Ward's meeting today, I understand what you're doing here. Let's keep it.

[JStickler]

LOL, just saw Trevor's comment and that you'd pulled it. That's OK too.

[JStickler]

Why not combine this with the example above? Curious as to why it's called out separately.

[Jayclifford345]

So I was going to ask you about this one. I currently have the first example using MinIO for test purposes and then provide the cloud storage configurations after. I have added the S3 one for now but currently testing Azure blog to also add next

[Jayclifford345]

Marking this as ready for review as we are getting quite a few questions in the community over helm deployment. Will create subsequent PR's with other further additions.

[trevorwhitney]

this looks good, but I don't think we should include the instructions for deploying with kind. I think that will just lead to questions about kind we are not experts in. There's a lot of ways to spin up a local k8s cluster, I think it's reasonable to expect someone familiar with helm to bring their own k8s cluster.

[Jayclifford345]

@JStickler @trevorwhitney , that's the kind deployment instructions deleted. Let me know if there are any other parts you think might need some rework

[grafanabot]

This PR must be merged before a backport PR will be created.