Skip to content
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

Reword Service Accounts docs #14681

Conversation

@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Jun 1, 2019
@k8s-ci-robot k8s-ci-robot added language/en Issues or PRs related to English language sig/docs Categorizes an issue or PR as relevant to SIG Docs. labels Jun 1, 2019
@netlify
Copy link

netlify bot commented Jun 1, 2019

Deploy preview for kubernetes-io-master-staging ready!

Built with commit 1024e1e

https://deploy-preview-14681--kubernetes-io-master-staging.netlify.com

- Typically, a cluster's User accounts might be synced from a corporate
database, where new user account creation requires special privileges and
{{< glossary_tooltip text="namespaces" term_id="namespace" >}} of a cluster.
Service accounts *are* namespaced; [human] user identities are not namespaced.
Copy link
Contributor

Choose a reason for hiding this comment

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

maybe we should avoid mixing 'user accounts' and 'user identities'.

@@ -10,99 +10,107 @@ weight: 50
---

{{% capture overview %}}
This is a Cluster Administrator guide to service accounts. It assumes knowledge of
This is a Cluster Operator guide to service accounts. It assumes knowledge of
Copy link
Contributor

Choose a reason for hiding this comment

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

I believe most of the contents in this page are for "administrators' rather than average users.

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 borrowed this wording from https://kubernetes.io/docs/reference/glossary/?all=true#term-cluster-operator

Maybe it doesn't make sense to have two separate documents explicitly aimed at people with different experience levels. Rather, we could have a detailed Reference-section guide and also a simpler Task guide.

Something for a future PR? I want to keep this one focused.

@sftim sftim force-pushed the 20190601_task_configure_service_account_reword branch from 4e17983 to 37ed864 Compare June 3, 2019 10:36
@@ -9,7 +9,7 @@ weight: 90
---

{{% capture overview %}}
A service account provides an identity for processes that run in a Pod.
A _service account_ provides an identity for processes that run in a Pod.
Copy link
Contributor

Choose a reason for hiding this comment

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

Service account vs service account?

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 think “service account” is fine for English grammar. The Kubernetes resource is ServiceAccount, which gets introduced below.

Copy link
Contributor

@kbhawkey kbhawkey Jun 3, 2019

Choose a reason for hiding this comment

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

Do you need italics, above and below? Check the style guide.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Tweaked

## Use the Default Service Account to access the API server.
## Use the default Service Account to access the API server

Each namespace has a default ServiceAccount, named `default`.
Copy link
Contributor

Choose a reason for hiding this comment

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

ServiceAccount is the resource?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yep.

Copy link
Contributor

Choose a reason for hiding this comment

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

OK. Check the heading.

@sftim sftim force-pushed the 20190601_task_configure_service_account_reword branch 3 times, most recently from 5c5e7e3 to 4f4805a Compare June 3, 2019 16:50
@sftim sftim force-pushed the 20190601_task_configure_service_account_reword branch from 4f4805a to 22a526d Compare June 3, 2019 18:22
@sftim
Copy link
Contributor Author

sftim commented Jun 3, 2019

I'd left “user account” in a heading. Fixed.
(this will break inbound links to that fragment, but as it's at the top of the page I'm not worried)

@@ -70,15 +76,17 @@ spec:
...
```

The pod spec takes precedence over the service account if both specify a `automountServiceAccountToken` value.
If both the ServiceAccount and the pod spec specify a value for
`automountServiceAccountToken`, the pod spec takes precedence.
Copy link
Contributor

Choose a reason for hiding this comment

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

PodSpec is the object

Copy link
Contributor Author

Choose a reason for hiding this comment

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

From a cluster operator's point of view, Pods have specifications. Pods are Kubernetes objects.
Maybe “the Pod's specification” or “the Pod's .spec”?

Copy link
Contributor

Choose a reason for hiding this comment

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

OK

between the concept of a user and a service account for a number of reasons:

- Users represent humans. Service accounts are for processes, which
run in {{< glossary_tooltip text="pods" term_id="pod" >}}.
Copy link
Contributor

Choose a reason for hiding this comment

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

  • I'm not sure this change helps clarify a user account vs. service account.
  • are italics needed?

@tengqm
Copy link
Contributor

tengqm commented Jun 4, 2019

/lgtm
When other feedbacks are addressed, we can move this in.

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jun 4, 2019
@sftim sftim changed the title Reword Service Accounts docs [WIP] Reword Service Accounts docs Jun 5, 2019
@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 Jun 5, 2019
@sftim sftim force-pushed the 20190601_task_configure_service_account_reword branch from 22a526d to d67e7d4 Compare July 11, 2019 08:00
@k8s-ci-robot k8s-ci-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jul 11, 2019
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please assign tengqm
You can assign the PR to them by writing /assign @tengqm in a comment when ready.

The full list of commands accepted by this bot can be found 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

@sftim sftim changed the title Reword Service Accounts docs [WIP] Reword Service Accounts docs Aug 3, 2019
@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 Aug 3, 2019
@sftim sftim force-pushed the 20190601_task_configure_service_account_reword branch from 0d1ff97 to 9668687 Compare August 3, 2019 09:18
@zacharysarah
Copy link
Contributor

@sftim 👋 Just checking in. Do you have what you need to continue?

@sftim
Copy link
Contributor Author

sftim commented Aug 6, 2019

Hi @zacharysarah
Yep, this does need more work but (I hope) not much more, and I've got feedback to draw on.

@sftim sftim force-pushed the 20190601_task_configure_service_account_reword branch from 9668687 to 66e78d6 Compare August 25, 2019 12:51
@sftim sftim changed the title [WIP] Reword Service Accounts docs Reword Service Accounts docs Aug 25, 2019
@k8s-ci-robot k8s-ci-robot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Aug 25, 2019
@sftim
Copy link
Contributor Author

sftim commented Aug 25, 2019

Revised

@sftim
Copy link
Contributor Author

sftim commented Sep 9, 2019

@chenopis or @tengqm - can you review?

@tengqm
Copy link
Contributor

tengqm commented Sep 25, 2019

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Sep 25, 2019
content_template: templates/task
weight: 90
---

{{% capture overview %}}
A service account provides an identity for processes that run in a Pod.
Kubernetes recognises two distinct ways for clients outside the
Copy link
Contributor

Choose a reason for hiding this comment

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

hello @sftim . I read through the page. There are a few minor nits that could be addressed before merging.
line 12: recognizes 😄
line 19: spelling yoy, recognizes
line 40: capitalize namespace or not?
line 61: the kubelet? enclose in backticks or not?
line 95: possible edit: You can list all ServiceAccount resources in your current namespace with:
line 120: possible edit: You can get a YAML output of ...
line 314: fix the link with forward slash before docs, projected volume type called

@sftim sftim changed the title Reword Service Accounts docs [WIP] Reword Service Accounts docs Sep 25, 2019
@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 Sep 25, 2019
@sftim sftim force-pushed the 20190601_task_configure_service_account_reword branch from 66e78d6 to 82b4734 Compare September 25, 2019 22:18
@k8s-ci-robot
Copy link
Contributor

New changes are detected. LGTM label has been removed.

@k8s-ci-robot k8s-ci-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Sep 25, 2019
@sftim sftim force-pushed the 20190601_task_configure_service_account_reword branch from 82b4734 to 1024e1e Compare September 25, 2019 22:24
@sftim
Copy link
Contributor Author

sftim commented Sep 25, 2019

Thanks for the feedback @kbhawkey
I think it's all fixed now(?)

@kbhawkey
Copy link
Contributor

@sftim , I read through the Configure ServiceAccounts ... page again. Some of the small nits remain (spelling:recognises) and there is a link to automatically that needs to be corrected. Also check for a typo where you changed the sentence about YAML output.
The second part of this PR, Managing ServiceAccounts, is missing the reference information about ServiceAccount automation and Kubernetes controllers. For me, this part of the page is the most important. I realize that there are some dependencies with this PR, but perhaps the controller content should stay with the page until the controller reference section is created in another commit (unless the content is entirely outdated).

@sftim
Copy link
Contributor Author

sftim commented Sep 27, 2019

I think what I'll do is close this PR, keep the branch around, and try to get these changes in once there are other Controller-related PRs already merged.
Thanks for all feedback so far.

@sftim sftim closed this Sep 27, 2019
@sftim sftim changed the title [WIP] Reword Service Accounts docs Reword Service Accounts docs Dec 12, 2019
@k8s-ci-robot k8s-ci-robot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Dec 12, 2019
@sftim sftim deleted the 20190601_task_configure_service_account_reword branch June 9, 2021 17:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. language/en Issues or PRs related to English language sig/docs Categorizes an issue or PR as relevant to SIG Docs. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants