-
Notifications
You must be signed in to change notification settings - Fork 14.4k
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
Tweak wording for Workloads overview #24602
Tweak wording for Workloads overview #24602
Conversation
Deploy preview for kubernetes-io-master-staging ready! Built with commit aa27de5 https://deploy-preview-24602--kubernetes-io-master-staging.netlify.app |
These resources configure {{< glossary_tooltip term_id="controller" text="controllers" >}} | ||
that make sure the right number of the right kind of Pod are running, to match the state | ||
that make sure the right number of the right kind of `Pod` are running, to match the state |
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.
@sftim , Can you explain the updates to the resource names? I'd like to understand if this is a change to the style guide?
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.
The style guide was updated: 826d53c
What do you think? Does this change make the page easier to follow, or harder?
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.
It is easier to have an explicit style rule that defines something like, "always add code formatting to API resource terms and always use the API term in the content as capitalized in the code".
It is not always clear when a common term like Pod needs to use capitalization. Often a page overuses the pod term. Some of the styling of the term Pod in the page could be removed, otherwise the page starts to look like a gameboard?
Per the style guide, the other API terms use code styling. Hopefully the added styling helps readers and does not detract from reading the page.
@sftim |
I invite reviewers to compare:
Which is better? If it's the second one: merge this, then iterate. |
712b525
to
ca38a6f
Compare
/approve cancel |
ca38a6f
to
dd53659
Compare
In the wider Kubernetes ecosystem, you can find third-party workload resources that provide | ||
additional behaviors. Using a | ||
[custom resource definition](/docs/concepts/extend-kubernetes/api-extension/custom-resources/), | ||
you can add in a third-party workload resource if you want a specific behavior that's not part |
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.
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.
I'd rather link to the concept than the API details, especially whilst the API details don't hyperlink back to the concept.
Pod is running means that all the Pods on that node fail. Kubernetes treats that level | ||
of failure as final: you would need to create a new Pod even if the node later recovers. | ||
`Pods` have a [defined lifecycle](/docs/concepts/workloads/pods/pod-lifecycle/). | ||
For example, once a `Pod` is running in your cluster then a critical fault on 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.
Is it possible to use lowercase for some of the pod terms in lines 15-19?
Line 12 is clear.
additional behaviors. Using a | ||
[custom resource definition](/docs/concepts/extend-kubernetes/api-extension/custom-resources/), | ||
you can add in a third-party workload resource if you want a specific behavior that's not part | ||
of Kubernetes itself. For example, if you want the ability to specify a task that runs just once |
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.
not part of Kubernetes itself
This is not accurate. The more common way is
not part of Kubernetes core
[custom resource definition](/docs/concepts/extend-kubernetes/api-extension/custom-resources/), | ||
you can add in a third-party workload resource if you want a specific behavior that's not part | ||
of Kubernetes itself. For example, if you want the ability to specify a task that runs just once | ||
at a specific future date, neither `Job` nor `CronJob` is right for that - but you can implement or |
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.
No. This can be done using CronJob.
Please think of a different example.
[`PersistentVolume`](/docs/concepts/storage/persistent-volumes/), and replicate both | ||
the pods and their storage across different failure zones. Your code, running in the `Pods`, |
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.
This introduction has gone too far from the core concept of StatefulSet. Multi-zone deployment is not limited to stateful apps. It is a different topic from stateful.
I'll move this back to Draft to mark that there's tweaks to make. |
dd53659
to
7e3338e
Compare
7e3338e
to
aa27de5
Compare
I'd like another review on this (not urgent). |
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.
This looks good to me, thank you @sftim!
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: onlydole 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 |
`Deployment` is a good fit for managing a stateless application workload on your cluster, | ||
where any `Pod` in the `Deployment` is interchangeable and can be replaced if needed. | ||
* [`StatefulSet`](/docs/concepts/workloads/controllers/statefulset/) lets you | ||
run one or more related Pods that do track state somehow. For example, if your workload |
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.
nit: rephrase/replace: that do track state somehow.
The use of "somehow" makes me think twice.
StatefulSet
workload resources let you manage stateful applications.
LGTM label has been added. Git tree hash: 6bced388dcbe1b24ca34b0dd38e10bb71e77650e
|
/lgtm |
/hold cancel |
Follows on from PR #23737