Add Helm and Kubernetes tutorial

[rynowak]

Thank you for helping make the Radius documentation better!

Please follow this checklist before submitting:

• Read the contribution guide
• Commands include options for Linux, MacOS, and Windows within codetabs
• New file and folder names are globally unique
• Page references use shortcodes instead of markdown or URL links
• Images use HTML style and have alternative text
• Places where multiple code/command options are given have codetabs

In addition, please fill out the following to help reviewers understand this pull request:

Description

Auto-generated description

🤖 Generated by Copilot at ffba503

Summary

🔄🚀📝

Updated the resourceType names in the rad_resource_list command reference to include the dapr prefix. This improves the clarity and consistency of the documentation for users who want to use dapr resources with radius-cli.

dapr prefix adds
clarity for resource types
cutting through the fog

Walkthrough

• Add dapr prefix to resourceType names for pubSubBrokers, stateStores, and secretStores to indicate compatibility with dapr runtime (link)

Issue reference

[willtsai]

Overall this looks really great! A couple of high-level points:

• Should the headers for each step include the word "step" in them to be consistent with other tutorials? e.g. "## Step 7. Add Connection"
• I worry that this tutorial is very long, maybe covering too much ground. Would it be a good idea to show only one of Steps 6 and 7? and then at the end you can refer the reader to the other how-tos for adding Radius features to their k8s helm app.

[AaronCrawfis]

Flow is looking really good. The steps seems like the right set, in the right order, and the way to "see" each effect seems spot on. Only major concern is how we can handle the Kubernetes secret before Radius. Left a comment there.

[github-actions]

Azure Static Web Apps: Your stage site is ready! Visit it here: https://calm-bush-0cc2a4f1e-864.westus2.3.azurestaticapps.net

[willtsai]

A few issues: At this deployment https://calm-bush-0cc2a4f1e-864.westus2.3.azurestaticapps.net/, the following does not render: image src=“diagram.png” The Tutorial name in the left nav bar ("Helm application") does not match the title of the tutorial ("Use Helm to run your first app"). They should be consistent and say something like "Use Helm to run your first Radius application" "Open Github codespaces button should open codespaces in a different browser tab by default so the reader can switch between a codespaces tab and tutorial tab. When I create a codespace and follow instructions, I get @jonvsm ➜ /workspaces/samples (v0.26) $ cd ./samples/demo @jonvsm ➜ /workspaces/samples/samples/demo (v0.26) $ rad init Failed to read Kubernetes config. Cause: open /home/codespace/.kube/config: no such file or directory.

regarding the opening in new tabs, we will have to make an adjustment to the overall website configs as this is the same behavior as the getting started guide.

[github-actions]

Azure Static Web Apps: Your stage site is ready! Visit it here: https://calm-bush-0cc2a4f1e-864.westus2.3.azurestaticapps.net

[github-actions]

Azure Static Web Apps: Your stage site is ready! Visit it here: https://calm-bush-0cc2a4f1e-864.westus2.3.azurestaticapps.net

[github-actions]

Azure Static Web Apps: Your stage site is ready! Visit it here: https://calm-bush-0cc2a4f1e-864.westus2.3.azurestaticapps.net

[willtsai]

Overall is looking good. One note: a lot of our how-to guides use ordered lists within the steps. Format similar to:

## Step 1: xxxxx

1. Do this
1. Do that

## Step 2: yyyy

1. Do this
1. Do that

This PR follows a different format that can cause a user to lose their place, without the ordered list:

## Step 1

Do this

Do that

Would it make sense to move to the former format?

addressed

I have addressed the feedback and gotten approval from another docs maintainer.