Move misplaced comment outside YAML block in storageclass-aws-ebs.yaml

[imuneeeb]

Description

This PR corrects a formatting issue in the StorageClass YAML configuration where a comment about tagSpecification was mistakenly included inside the YAML block. The comment is now moved outside the YAML block for better clarity.

Changes Made

• Moved the comment about tagSpecification outside the YAML block.

Issue

Closes: #

[netlify]

✅ Pull request preview available for checking

Built without sensitive environment variables

Name	Link
🔨 Latest commit	42824fe
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-io-main-staging/deploys/6740f06537e17c0008609bd1
😎 Deploy Preview	https://deploy-preview-48809--kubernetes-io-main-staging.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[netlify]

✅ Pull request preview available for checking

Built without sensitive environment variables

Name	Link
🔨 Latest commit	96bf9f5
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-io-main-staging/deploys/67436822b440f60008e6c790
😎 Deploy Preview	https://deploy-preview-48809--kubernetes-io-main-staging.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[sftim]

@imuneeeb, why should we make this change? The PR description doesn't explain.

[imuneeeb]

@sftim Description added

[sftim]

This PR corrects a formatting issue in the StorageClass YAML configuration where a comment about tagSpecification was mistakenly included inside the YAML block. The comment is now moved outside the YAML block for better clarity.

#48054 (comment) did suggest the same thing. However, there is something to be said for leaving it in place.

If a person fetches https://k8s.io/examples/storage/storageclass/storageclass-aws-ebs.yaml directly, they see the comment. Maybe that's useful to keep.

Anyway: the change behaves as described, so:
LGTM

[tengqm]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: tengqm

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• content/en/OWNERS [tengqm]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 8007c7d5a0220ead0c0f744e535e1b0640e5432c