Skip to content

Conversation

HirazawaUi
Copy link
Contributor

Description

Add a blog for KEP-3721

Relate: kubernetes/enhancements#3721

Issue

Closes: #

@k8s-ci-robot k8s-ci-robot added this to the 1.34 milestone Jul 7, 2025
@k8s-ci-robot k8s-ci-robot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jul 7, 2025
Copy link

netlify bot commented Jul 7, 2025

👷 Deploy Preview for kubernetes-io-vnext-staging processing.

Name Link
🔨 Latest commit f67da6c
🔍 Latest deploy log https://app.netlify.com/projects/kubernetes-io-vnext-staging/deploys/686fd8300a919700082b7062

@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. area/blog Issues or PRs related to the Kubernetes Blog subproject labels Jul 7, 2025
@k8s-ci-robot k8s-ci-robot added language/en Issues or PRs related to English language size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Jul 7, 2025
Copy link

netlify bot commented Jul 7, 2025

Pull request preview available for checking

Built without sensitive environment variables

Name Link
🔨 Latest commit b6f21b6
🔍 Latest deploy log https://app.netlify.com/projects/kubernetes-io-main-staging/deploys/68a463ab4c1be60008b7af50
😎 Deploy Preview https://deploy-preview-51529--kubernetes-io-main-staging.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

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

@aibarbetta
Copy link
Member

Hi @ajaysundark @HirazawaUi 👋 this is Agus from the v1.34 Communications Team!

@ajaysundark as author of #51428, I'd like you to be a writing buddy for @HirazawaUi on this PR.

Please:

  • Review this PR, paying attention to the guidelines and review hints
  • Update your own PR based on any best practices you identify that should be applied
  • Remember to be compassionate with your fellow article author

@k8s-ci-robot k8s-ci-robot added area/localization General issues or PRs related to localization area/web-development Issues or PRs related to the kubernetes.io's infrastructure, design, or build processes language/zh Issues or PRs related to Chinese language sig/docs Categorizes an issue or PR as relevant to SIG Docs. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. and removed size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Jul 10, 2025
@HirazawaUi HirazawaUi changed the base branch from dev-1.34 to main July 10, 2025 15:12
@k8s-ci-robot k8s-ci-robot added size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. and removed size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. labels Jul 10, 2025
@aibarbetta
Copy link
Member

/sig release

@k8s-ci-robot k8s-ci-robot added the sig/release Categorizes an issue or PR as relevant to SIG Release. label Jul 13, 2025
@windsonsea
Copy link
Member

/remove-language zh
/remove-area localization

@k8s-ci-robot k8s-ci-robot removed language/zh Issues or PRs related to Chinese language area/localization General issues or PRs related to localization labels Jul 21, 2025
@aibarbetta
Copy link
Member

Hi @HirazawaUi 👋 -- this is Agus from the v1.34 Communications Team!

Just a friendly reminder that we are approaching the feature blog "ready for review" deadline: Friday 8th August 2025. We ask you to have the blog in non-draft state, and all write-up to be complete.

If you have any questions or need help, please don't hesitate to reach out to me or any of the Communications Team members. We are here to help you!

Comment on lines 76 to 81
The `emptyDir` volumes do not provide the same [security protections as Secrets](https://kubernetes.io/docs/concepts/configuration/secret/#information-security-for-secrets).
so if security is a top concern, stick with Secrets where possible.
We’ll make sure the docs call this out clearly. No newline at end of file
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is really bad advice. Using this new mechanism may actually provide better information security that Secret.

Only include this statement if you can get a SIG Security person, ideally a tech lead for SIG Security, to endorse that inclusion.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can I avoid involving the SIG Security maintainers by removing the description of the secret? They aren’t familiar with this feature and might unnecessarily spend extra time understanding it :)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've rephrited this, specifically avoiding mention of secret and instead emphasized that this feature is unsuitable for storing sensitive data without adequate and appropriate cluster security policies. Do you think this is sufficient? Or do we still need a technical review from SIG Security?

@lmktfy
Copy link
Contributor

lmktfy commented Aug 10, 2025

/hold

I have a strong concern: see #51529 (comment)

OK to unhold if either:

  • the article doesn't include that statement any more
  • SIG Security have endorsed leaving it in

@k8s-ci-robot k8s-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Aug 10, 2025
@k8s-ci-robot k8s-ci-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Aug 11, 2025
@HirazawaUi HirazawaUi force-pushed the add-3721-blog branch 2 times, most recently from e21f134 to a2c5008 Compare August 17, 2025 15:33

If storing sensitive data like keys or tokens using this feature,
ensure your cluster security policies effectively protect nodes
against unauthorized access to prevent exposure of confidential information. No newline at end of file
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
against unauthorized access to prevent exposure of confidential information.
against unauthorized access to prevent exposure of confidential information.
## Summary
This feature will eliminate a number of complex workarounds used today, simplifying
apps authoring, and opening doors for more use cases. Kubernetes stays flexible and
open for feedback. Tell us how you use this feature or what is missing.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! Added.

Copy link
Member

@SergeyKanzhelev SergeyKanzhelev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Aug 18, 2025
@k8s-ci-robot
Copy link
Contributor

LGTM label has been added.

Git tree hash: 2aecd50bbfcc1a0b06ea26e68ea6a2bd5c243740

@k8s-ci-robot k8s-ci-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Aug 19, 2025
@aibarbetta
Copy link
Member

With SIG and Comms review done, assigning to SIG Docs Blog for approval
/assign @graz-dev

Copy link
Contributor

@graz-dev graz-dev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It looks good to me.

/hold cancel
/lgtm
/approve

@k8s-ci-robot k8s-ci-robot added lgtm "Looks good to me", indicates that a PR is ready to be merged. and removed do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. labels Aug 20, 2025
@k8s-ci-robot
Copy link
Contributor

LGTM label has been added.

Git tree hash: 1cf7d42619f75ea77509658f38d236f5cceb067c

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: graz-dev, SergeyKanzhelev

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:

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 k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 20, 2025
@k8s-ci-robot k8s-ci-robot merged commit 8234883 into kubernetes:main Aug 20, 2025
6 checks passed
@graz-dev graz-dev mentioned this pull request Sep 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. area/blog Issues or PRs related to the Kubernetes Blog subproject cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. language/en Issues or PRs related to English language lgtm "Looks good to me", indicates that a PR is ready to be merged. sig/docs Categorizes an issue or PR as relevant to SIG Docs. sig/release Categorizes an issue or PR as relevant to SIG Release. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants