Never render secrets into values.yaml

[davidfowl]

Description

Don't render generated secrets in values.yaml

Checklist

• Is this feature complete?
  • Yes. Ready to ship.
• Are you including unit tests for the changes and scenario tests if relevant?
  • Yes
• Did you add public API?
  • No
• Does the change make any security assumptions or guarantees?
  • Yes
    • If yes, have you done a threat model and had a security review?
      • Yes
      • No
  • No
• Does the change require an update in our Aspire docs?
  • No

[Copilot]

Pull Request Overview

This PR prevents rendering generated secret values into values.yaml by ensuring that parameters marked as secrets do not include their values in Helm chart outputs.

• Modified test cases to add a new secret parameter "param3".
• Updated expected values in the test fixtures to include "param3" in the secrets section.
• Updated the Kubernetes resource context to conditionally omit secret values.

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File	Description
tests/Aspire.Hosting.Kubernetes.Tests/KubernetesPublisherTests.cs	Adds a new secret parameter "param3" and includes it in the environment configuration.
tests/Aspire.Hosting.Kubernetes.Tests/ExpectedValues.cs	Extends expected YAML output to accommodate "param3" as a secret.
src/Aspire.Hosting.Kubernetes/KubernetesResourceContext.cs	Updates value assignment logic to prevent rendering secret values in values.yaml.