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

[GarbageCollector] update user guide #1152

Merged
merged 1 commit into from
Sep 15, 2016

Conversation

caesarxuchao
Copy link
Member

@caesarxuchao caesarxuchao commented Sep 2, 2016

cc @kubernetes/docs


This change is Reviewable

@caesarxuchao caesarxuchao added this to the 1.4 milestone Sep 2, 2016
@lavalamp lavalamp assigned mbohlool and unassigned lavalamp Sep 2, 2016
@caesarxuchao
Copy link
Member Author

@mbohlool friendly ping :)

@caesarxuchao
Copy link
Member Author

Thanks @mbohlool. @devin-donnelly do I need more label to get it merged?

@caesarxuchao caesarxuchao reopened this Sep 7, 2016
@mbohlool
Copy link
Contributor

mbohlool commented Sep 7, 2016

I guess This PR may need a DOC LGTM (by a tech writer). If that is the case, I would suggest we send these type of changes initiated by developers directly to tech writers as they make sense to an engineer (the PR owner) and validating the truth of the statement is not part of another developer's review. There is not much value in having another developer review these changes, having a tech writer as reviewer should be enough.

@caesarxuchao
Copy link
Member Author

#1159 will fix the travis failure

@devin-donnelly
Copy link
Contributor

Review status: 0 of 2 files reviewed at latest revision, 10 unresolved discussions.


_data/guides.yml, line 61 [r1] (raw file):

  - title: Using kubectl to Manage Resources
    path: /docs/user-guide/working-with-resources/
  - title: Garbage collection (Beta)

Capitalize the "C" in "collection


docs/user-guide/garbage-collector.md, line 11 [r1] (raw file):

{:toc}

## Garbage Collector is a beta feature and is enabled by default

Is this the main header? If so, change to just "Garbage Collection".

Afterward add a paragraph: "Note: the Garbage Collector is a beta feature and enabled by default in Kubernetes version 1.4."


docs/user-guide/garbage-collector.md, line 13 [r1] (raw file):

## Garbage Collector is a beta feature and is enabled by default

### What is garbage collector for

Change heading to "What Does Garbage Collection Do?"


docs/user-guide/garbage-collector.md, line 15 [r1] (raw file):

### What is garbage collector for

When a replica set is deleted, in many cases it is desirable that server will automatically garbage collects all the pods created by the replica set. The garbage collector (GC) implements this. Generally, when an owner is deleted, GC deletes its dependents.

Passive voice.

"When you delete a replica set, it is often desirable for the server [editorial note: should this be "Master"?] to automatically garbage collect all the pods that the replica set has created. When you delete an owner object, the Garbage Collector (GC) deletes that owner's dependent objects.


docs/user-guide/garbage-collector.md, line 17 [r1] (raw file):

When a replica set is deleted, in many cases it is desirable that server will automatically garbage collects all the pods created by the replica set. The garbage collector (GC) implements this. Generally, when an owner is deleted, GC deletes its dependents.

### How to establish owner-dependent relation

"How to establish an owner-dependent relationship between objects"


docs/user-guide/garbage-collector.md, line 19 [r1] (raw file):

### How to establish owner-dependent relation

In release 1.3, a `metadata.ownerReferences` field is introduced to every Kubernetes API objects. When an object has an `ownerReference` pointing to another object, the dependent-owner relation is established.

More passive voice.

"Kubernetes added 1.3 added a metadata.ownerReferences field to every Kubernetes API object. If an API object is a dependent of another object, ownerReference should point to the owning API object.


docs/user-guide/garbage-collector.md, line 21 [r1] (raw file):

In release 1.3, a `metadata.ownerReferences` field is introduced to every Kubernetes API objects. When an object has an `ownerReference` pointing to another object, the dependent-owner relation is established.

In release 1.4, Kubernetes control plane will automatically set a pod to have an ownerReference pointing to the replication controller or the replica set that creates it.

"When you create a Replication Controller or ReplicaSet in Kubernetes 1.4, the Kubernetes control plane automatically sets the ownerReference field for each pod that set creates.


docs/user-guide/garbage-collector.md, line 23 [r1] (raw file):

In release 1.4, Kubernetes control plane will automatically set a pod to have an ownerReference pointing to the replication controller or the replica set that creates it.

To set up owner-dependent relation among other objects, you can manually update the `ownerReferences` field of the dependent objects.

You can set up owner-dependent relationships among other objects in the Kubernetes API by manually setting the ownerReference field on dependent objects.


docs/user-guide/garbage-collector.md, line 25 [r1] (raw file):

To set up owner-dependent relation among other objects, you can manually update the `ownerReferences` field of the dependent objects.

### How to request the garbage collector to delete or not delete dependents

Change to "Controlling how Garbage Collector deletes dependents"


docs/user-guide/garbage-collector.md, line 27 [r1] (raw file):

### How to request the garbage collector to delete or not delete dependents

When deleting an object, you can request the GC to ***asynchronously*** delete its dependents by ***explicitly*** specifying `deleteOptions.orphanDependents=false` in the deletion request sent to the API server. A 200 OK response from the API server indicates the owner is deleted.

"in the deletion request that you send to the API server."


Comments from Reviewable

@devin-donnelly
Copy link
Contributor

Some writerly comments. Once those are cleared up, we can merge.

@caesarxuchao
Copy link
Member Author

Review status: 0 of 2 files reviewed at latest revision, 10 unresolved discussions.


docs/user-guide/garbage-collector.md, line 15 [r1] (raw file):

Previously, devin-donnelly wrote…

Passive voice.

"When you delete a replica set, it is often desirable for the server [editorial note: should this be "Master"?] to automatically garbage collect all the pods that the replica set has created. When you delete an owner object, the Garbage Collector (GC) deletes that owner's dependent objects.

The first sentence is one specific use case. Then I say the garbage collector fulfills this use case. And the last sentence abstracts the function of the garbage collector. I don't think the edits express this, so I changed the paragraph differently from your suggestion. PTAL.

docs/user-guide/garbage-collector.md, line 21 [r1] (raw file):

Previously, devin-donnelly wrote…

"When you create a Replication Controller or ReplicaSet in Kubernetes 1.4, the Kubernetes control plane automatically sets the ownerReference field for each pod that set creates.

I modified it different. PTAL.

Comments from Reviewable

@caesarxuchao
Copy link
Member Author

@devin-donnelly thank you! I modified some sentences differently. PTAL.

@devin-donnelly
Copy link
Contributor

Review status: 0 of 2 files reviewed at latest revision, 10 unresolved discussions.


docs/user-guide/garbage-collector.md, line 15 [r1] (raw file):

Previously, caesarxuchao (Chao Xu) wrote…

The first sentence is one specific use case. Then I say the garbage collector fulfills this use case. And the last sentence abstracts the function of the garbage collector. I don't think the edits express this, so I changed the paragraph differently from your suggestion. PTAL.

Only change I'd make is to say "When you delete, for example, a ReplicaSet"

(I'd use the actual API name "ReplicaSet" as well)


docs/user-guide/garbage-collector.md, line 17 [r1] (raw file):

Previously, devin-donnelly wrote…

"How to establish an owner-dependent relationship between objects"

object -> objects

docs/user-guide/garbage-collector.md, line 21 [r1] (raw file):

Previously, caesarxuchao (Chao Xu) wrote…

I modified it different. PTAL.

Still has incorrect grammar. Maybe change to "automatically sets the `ownerReference` field for each pod that the ReplicationController or ReplicaSet creates."

Comments from Reviewable

@devin-donnelly
Copy link
Contributor

Almost there. :) Thanks.

@devin-donnelly
Copy link
Contributor

docs/user-guide/garbage-collector.md, line 22 [r2] (raw file):

Kubernetes 1.3 added a metadata.ownerReferences field to every Kubernetes API object. If an API object is a dependent of another object, ownerReference should point to the owning API object.

When you create a replication controller or a replica set in Kubernetes 1.4, the Kubernetes control plane automatically sets the ownerReference field for each created pod to the replication controller or the replica set.

"the Kubernetes control plane automatically sets the ownerReference field in each created pod to point to the owning ReplicationController or ReplicaSet."


Comments from Reviewable

@caesarxuchao
Copy link
Member Author

Review status: 0 of 2 files reviewed at latest revision, 11 unresolved discussions.


docs/user-guide/garbage-collector.md, line 15 [r1] (raw file):

Previously, devin-donnelly wrote…

Only change I'd make is to say "When you delete, for example, a ReplicaSet"

(I'd use the actual API name "ReplicaSet" as well)

Thanks. I changed to use "ReplicaSet", "ReplicationController", "Pod" throughout the doc.

Comments from Reviewable

@caesarxuchao
Copy link
Member Author

Comments addressed. Thank you @devin-donnelly!

I also changed the file name from garbage-collector.md to garbage-collection.md

@devin-donnelly
Copy link
Contributor

LGTM. Would you mind fixing the merge conflict? It's preventing me from merging.

@caesarxuchao
Copy link
Member Author

@devin-donnelly sorry for the delay I was solving a P0 bug in the day. Rebased. PTAL. Thanks.

@devin-donnelly
Copy link
Contributor

Awesome, no problem. Merging in now.

@devin-donnelly devin-donnelly merged commit 6dd2eae into kubernetes:release-1.4 Sep 15, 2016

## Garbage Collection

Note: the Garbage Collection is a beta feature and is enabled by default in Kubernetes version 1.4.
Copy link
Member

Choose a reason for hiding this comment

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

@caesarxuchao this doc may be a good place to list behavior differences with/without the garbage collector, too.

Copy link
Member

Choose a reason for hiding this comment

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

(in an followup)

Okabe-Junya pushed a commit to Okabe-Junya/website that referenced this pull request Dec 4, 2023
* Localize term  site_reliabilty_engineering

Signed-off-by: Tania Duggal <[email protected]>

* Localize site-reliability-engineering.md into Hindi

Signed-off-by: Tania Duggal <[email protected]>

Signed-off-by: Tania Duggal <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants