-
Notifications
You must be signed in to change notification settings - Fork 14.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add blog post to reflect state of PodReadyToStartContainersCondition #43932
Conversation
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
/retitle Add blog post to reflect state of PodReadyToStartContainersCondition |
/sig node |
Generally, you want to explain a bit more about what this feature is. And maybe to explain what users are seeing. Most people are not aware of this feature so the blog brings attention to it. |
I'll try my best to rephrase |
|
||
|
||
With Kubernetes 1.29 the PodReadyToStartContainersCondition functionality entered beta and is available by default. | ||
A new kubelet-managed pod condition in the status field of a pod. The kubelet will use the PodHasNetwork condition to accurately surface the initialization state of a pod, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A new kubelet-managed pod condition in the status field of a pod. The kubelet will use the PodHasNetwork condition to accurately surface the initialization state of a pod, | |
A new kubelet-managed pod condition in the status field of a pod. The kubelet will use the PodReadyToStartContainers condition to accurately surface the initialization state of a pod, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Style nit: condition names should be inside backticks. This helps people tell them apart from API kinds (which we write without backticks).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
updated Kevin's comment.
Style nit: condition names should be inside backticks. This helps people tell them apart from API kinds (which we write without backticks).
can you list me an example? I'm not quite getting this. sorry for my poor English
content/en/blog/_posts/2023-11-14-PodReadyToStartContainersCondition-in-beta.md
Outdated
Show resolved
Hide resolved
Hi @charles-chenzz! how are you? Here from the Communications Release Team 1.29, the deadline for the feature blog to be ready to review is this Friday, Nov 17th, the proposal publish date will be Dec 14th. cc: @a-mccarthy @kcmartin. It's related the feature blog about this KEP-4138 @kubernetes/sig-docs-blog-owners: Blog scheduled: Dec 14th, Publication Order Nro:2 |
I think we're already in the review process, no? |
1cfd572
to
d3a8ddf
Compare
What we're asking is for you to get this PR to the point where you believe it's ready to merge. |
content/en/blog/_posts/2023-11-14-PodReadyToStartContainersCondition-in-beta.md
Outdated
Show resolved
Hide resolved
content/en/blog/_posts/2023-11-14-PodReadyToStartContainersCondition-in-beta.md
Outdated
Show resolved
Hide resolved
content/en/blog/_posts/2023-11-14-PodReadyToStartContainersCondition-in-beta.md
Outdated
Show resolved
Hide resolved
content/en/blog/_posts/2023-11-14-PodReadyToStartContainersCondition-in-beta.md
Outdated
Show resolved
Hide resolved
content/en/blog/_posts/2023-11-14-PodReadyToStartContainersCondition-in-beta.md
Outdated
Show resolved
Hide resolved
content/en/blog/_posts/2023-11-14-PodReadyToStartContainersCondition-in-beta.md
Outdated
Show resolved
Hide resolved
content/en/blog/_posts/2023-11-14-PodReadyToStartContainersCondition-in-beta.md
Outdated
Show resolved
Hide resolved
|
||
### How can I learn more? | ||
|
||
Please check out the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe link the KEP also?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For example, maybe a sentence like the following:
For more detailed overview of the feature, please read KEP-3085.
Also maybe mention other blog posts around this feature ie https://kubernetes.io/blog/2022/09/14/pod-has-network-condition/
But maybe that is too much..
Therefore, there is a need for an improved mechanism to provide cluster administrators with a clear and | ||
comprehensive view of pod sandbox creation completion and container readiness. | ||
|
||
## What's the benefit? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe we can mention CSI creation in relation to volumes and configmaps.
I stumbled upon this feature because I was looking for a programmatic way to detect failures in mounting volumes from missing Secrets/ConfigMaps.
content/en/blog/_posts/2023-11-14-PodReadyToStartContainersCondition-in-beta.md
Outdated
Show resolved
Hide resolved
updated to latest date |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
nice work @charles-chenzz
I barely helped with this so I wouldn’t be upset if you removed me from authors.
/approve Please consider squashing this to 1 commit @charles-chenzz |
d64fd3e
to
9d4cf90
Compare
squashed to one commit. can re-lgtm if you don't mind |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry; we reviewed this before but actually I recommend some fixes. Please see the inline feedback.
/lgtm cancel
content/en/blog/_posts/2023-12-19-PodReadyToStartContainersCondition-in-beta.md
Outdated
Show resolved
Hide resolved
content/en/blog/_posts/2023-12-19-PodReadyToStartContainersCondition-in-beta.md
Outdated
Show resolved
Hide resolved
content/en/blog/_posts/2023-12-19-PodReadyToStartContainersCondition-in-beta.md
Outdated
Show resolved
Hide resolved
content/en/blog/_posts/2023-12-19-PodReadyToStartContainersCondition-in-beta.md
Outdated
Show resolved
Hide resolved
content/en/blog/_posts/2023-12-19-PodReadyToStartContainersCondition-in-beta.md
Outdated
Show resolved
Hide resolved
content/en/blog/_posts/2023-12-19-PodReadyToStartContainersCondition-in-beta.md
Outdated
Show resolved
Hide resolved
9d4cf90
to
bf39bb3
Compare
update as suggested |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One more thing to fix, please.
content/en/blog/_posts/2023-12-19-PodReadyToStartContainersCondition-in-beta.md
Outdated
Show resolved
Hide resolved
bf39bb3
to
1f6f75d
Compare
🛑 Do not merge until Kubernetes v1.29 is released 🛑 /lgtm |
LGTM label has been added. Git tree hash: a09a04a43972fd38a38feed81c6c9befbf989581
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sftim 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 |
/unhold |
this PR add blog post to reflect the state of feature: podreadytostartcontainerscondition