jiebi/CodeConvo huggingface dataset:
Change:
<!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!--Required Information--This is a... <!-- choose one by changing [ ] to [x] --- [ ] Feature Request [x] Bug Report Problem: identified for Kubernetes Secrets should indicate that the secrets stored in YAML files must be protected. Proposed Solution: Add Risk Bullet: If a Base64 encoded secret is shared, it should be considered Compromised. For Example: Checking into source control, placing on a document share, or emailing All of these expose your secret to everyone who has access. Base64 is considered so secrets encoded as Base64 require additional controls to ensure only authorized users/systems can access them. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
Add the bullet above under the following section:
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. Prevent issues from auto-closing with an comment. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale
issue solved.

Discussion:
- Administrators should limit access to etcd to admin users - Secret data in the API server is at rest on the disk that etcd uses; admins may want to wipe/shred disks used by etcd when no longer in use <ins> - If you configure the secret through a manifest (JSON or YAML) file which has the secret data encoded as base64, sharing this file or checking it in to a source repository means the secret is compromised. Base64 encoding is not an encryption method and is considered the same as plain text. </ins> - Applications still need to protect the value of secret after reading it from the volume, such as not accidentally logging it or transmitting it to an untrusted party. - A user who can create a pod that uses a secret can also see the value of that secret.  Even
Change:
ClusterReplicaSetPreferences docs point to a source code file in the main repo This also happens in /docs/tasks/administer-federation/replicaset/
Do you mean FederatedReplicaSetPreference? I can't find ClusterReplicaSetPreference
exactly! FederatedReplicaSetPreference is correct. Sorry for it
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. Prevent issues from auto-closing with an comment. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale
/remove-lifecycle stale
/assign

Discussion:
if you have 3 registered clusters and you create a federated ReplicaSet with `spec.replicas = 9`, then each ReplicaSet in the 3 clusters will have `spec.replicas=3`. <del> To modify the number of replicas in each cluster, you can specify [FederatedReplicaSetPreference](https://github.com/kubernetes/federation/blob/{{page.githubbranch}}/apis/federation/types.go) as an annotation with key `federation.kubernetes.io/replica-set-preferences` on the federated ReplicaSet. </del> <ins> To modify the number of replicas in each cluster, you can add an annotation with key `federation.kubernetes.io/replica-set-preferences` to the federated ReplicaSet. The value of the annoation is a serialized JSON that contains fields shown in the following example: ``` { "rebalance": true, "clusters": { "foo": { "minReplicas": 10, "maxReplicas": 50, "weight": 100 }, "bar": { "minReplicas": 10, "maxReplicas": 100, "weight": 200 } } } ``` The `rebalance` boolean field specifies whether replicas already scheduled and running may be moved in order to match current state to the specified preferences. The `clusters` object field contains a map where users can specify the constraints for replica placement across the clusters (`foo` and `bar` in the example). For each cluster, you can specify the minimum number of replicas that should be assigned to it (default is zero), the maximum number of replicas the cluster can accept (default is unbounded) and a number expressing the relative weight of preferences to place additional replicas to that cluster. </ins> ## Updating a Federated ReplicaSet
Change:
<!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!--Required Information--This is a... <!-- choose one by changing [ ] to [x] --- [ ] Feature Request [X] Bug Report Problem: Documentation example for environment variables only shows one variable, so it is not clear to users how to add a second or subsequent variables Proposed Solution: Add a second variable to the example. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. Prevent issues from auto-closing with an comment. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale
/remove-lifecycle stale /assign

Discussion:
HOSTNAME=envar-demo ... DEMO_GREETING=Hello from the environment <ins> DEMO_FAREWELL=Such a sweet sorrow </ins> 1. To exit the shell, enter `exit`.

env: - name: DEMO_GREETING value: "Hello from the environment" <ins> - name: DEMO_FAREWELL value: "Such a sweet sorrow" </ins>
Change:
<!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!--Required Information--This is a... <!-- choose one by changing [ ] to [x] --- [x] Feature Request [ ] Bug Report Problem: In the 4th paragraph in the "What is a Pod?" section, there is a sentence: "Containers in different pods have distinct IP addresses and can not communicate by IPC." The paragraph seems to imply that different pods communicate via IP. But it is not clarified. Proposed Solution: Please clarify how different pods communicate since they cannot use IPC. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. Prevent issues from auto-closing with an comment. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale
/remove-lifecycle stale /assign

Discussion:
can find each other via `localhost`. They can also communicate with each other using standard inter-process communications like SystemV semaphores or POSIX shared memory.  Containers in different pods have distinct IP addresses <del> and can not communicate by IPC. </del> <ins> and can not communicate by IPC without [special configuration](/docs/concepts/policy/pod-security-policy/). These containers usually communicate with each other via Pod IP addresses. </ins> Applications within a pod also have access to shared volumes, which are defined as part of a pod and are made available to be mounted into each application's
Change:
<!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!--Required Information--This is a... <!-- choose one by changing [ ] to [x] --- [ ] Feature Request [x] Bug Report Problem: The Table of Solutions should mention Calico with a pointer into the Calico docs. Probably with one pretty general row. Proposed Solution: Add one row with IaaS-Provider=any, Config-Mgmt=any, OS=any, Networking=any, , Support=Commercial and Community Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
CC
should we close this ?
Yeah, it looks resolved.

Discussion:
OpenStack Heat       | Saltstack    | CentOS | Neutron + flannel hostgw | [docs](/docs/getting-started-guides/openstack-heat)            |  Community ([@FujitsuEnablingSoftwareTechnologyGmbH](https://github.com/FujitsuEnablingSoftwareTechnologyGmbH)) Rackspace            | CoreOS       | CoreOS | flannel     | [docs](/docs/getting-started-guides/rackspace)                              |  Community ([@doublerr](https://github.com/doublerr)) any                  | any          | any    | any         | [docs](/docs/getting-started-guides/scratch)                                |  Community ([@erictune](https://github.com/erictune)) <ins> any                  | any          | any    | any         | [docs](http://docs.projectcalico.org/v2.2/getting-started/kubernetes/installation/)                                |  Commercial and Community </ins> **Note**: The above table is ordered by version test/used in nodes, followed by support level.
Change:
<!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!--Required Information--This is a... <!-- choose one by changing [ ] to [x] --- [ ] Feature Request [x] Bug Report Problem: Proposed Solution: Instructions for conjure-up installation with snap do not work if snapd was just installed. Re-login may be required. Page to Update: Instead of: it should be: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
Added the fix for this because it seemed like we just need an additional comment in the instructions.
We can close this issue now
Great, thanks!

Discussion:
``` sudo snap install conjure-up --classic <ins> # re-login may be required at that point if you just installed snap utility </ins> conjure-up kubernetes ```
Change:
<!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!--Required Information--This is a... <!-- choose one by changing [ ] to [x] --- [ ] Feature Request [x] Bug Report Problem: This works only for TCP ports, documentation should mention it. Proposed Solution: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. Prevent issues from auto-closing with an comment. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale
/remove-lifecycle stale /assign

Discussion:
is running the Redis server. With this connection in place you can use your local workstation to debug the database that is running in the pod. <ins> **Warning**: Due to known limitations, port forward today only works for TCP protocol. The support to UDP protocol is being tracked in [issue 47862](https://github.com/kubernetes/kubernetes/issues/47862). {: .warning} </ins> {% endcapture %}
Change:
<!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!--Required Information--This is a... <!-- choose one by changing [ ] to [x] --- [ ] Feature Request [x] Bug Report Problem: I follow the instruction but when i create mysql deployment, kubernetes is actually creating new disk instead of using my . here is the output of Proposed Solution: Explain clearer how is working Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
I dig deeper look like the PV i created in tutorial has empty . Thats why its not matched and new PV get created when i created PVC.
Pull Request submit
Closing because merged.

Discussion:
spec: accessModes: - ReadWriteOnce <ins> storageClassName: "" </ins> resources: requests: storage: 20Gi
Change:
uses title Encrypting data at rest which gives the impression, it's any data whereas it's only for Secrets. This term is widely used for storage/database systems and in this case it does not really mean that. A more accurate title would be Encrypting Secrets at rest. What do you think (Not to mention, it doesn't tell you anything that it's going to be about Secrets when you look at the left sidebar) !
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. Prevent issues from auto-closing with an comment. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale
/remove-lifecyle stale /assign

Discussion:
--- approvers: - smarterclayton <del> title: Encrypting data at rest </del> <ins> title: Encrypting Secret Data at Rest </ins> --- {% capture overview %}
Change:
<!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!--Required Information--This is a... <!-- choose one by changing [ ] to [x] --- [x] Feature Request [ ] Bug Report Problem: No examples Proposed Solution: Add this text: Here's a small example of how to see the structure of data and how to select some parts of it using jsonpaths Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. Prevent issues from auto-closing with an comment. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale
/remove-lifecycle stale /assign

Discussion:
?()      | filter             | {.users[?(@.name=="e2e")].user.password} | secret range, end | iterate list | {range .items[*]}[{.metadata.name}, {.status.capacity}] {end} | [127.0.0.1, map[cpu:4]] [127.0.0.2, map[cpu:8]] ""       | quote interpreted string | {range .items[*]}{.metadata.name}{"t"}{end} | 127.0.0.1    127.0.0.2 <ins> Below are some examples using jsonpath: ```shell $ kubectl get pods -o json $ kubectl get pods -o=jsonpath='{@}' $ kubectl get pods -o=jsonpath='{.items[0]}' $ kubectl get pods -o=jsonpath='{.items[0].metadata.name}' $ kubectl get pods -o=jsonpath='{range .items[*]}{.metadata.name}{"t"}{.status.startTime}{"n"}{end}' ``` </ins>
Change:
I wrote a crawl to fetch all the invalid herf in website: This is my Run this command: go run Then we can find some invalid herf. I fixes part of them: But I found that there are so many invalid herf. (part of them) I opened this issue to trace the invalid herf.
may have interest to this issue.
Thanks , We have a similar tool, right? . This would be a good supplement.
We do have a tool, but it might be good to also have a published script that anyone else can run too.

Discussion:
[1]: https://docs.mesosphere.com/latest/usage/service-guides/hdfs/ [2]: https://docs.mesosphere.com/latest/usage/service-guides/spark/ <del> [3]: https://docs.mesosphere.com/latest/usage/service-guides/chronos/ </del> <ins> [3]: https://mesos.github.io/chronos/docs/getting-started.html </ins> [4]: https://releases.k8s.io/{{page.githubbranch}}/cluster/addons/dns/README.md [5]: https://dcos.io/docs/latest/administration/installing/cloud/gce/ [6]: http://mesos.apache.org/
Change:
<!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!--Required Information--The typo in the example. The first "game-config-2" shall be "game-config"? <!-- choose one by changing [ ] to [x] --- [ ] Feature Request [x] Bug Report Problem: The typo in the example. The first "game-config-2" shall be "game-config"? I believe the game-config-2 is the name of configuremap in 2nd example. Proposed Solution: Change the first "game-config-2" shall be "game-config"? Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
kubectl describe configmaps game-config Name: game-config Namespace: default Labels: <noneAnnotations: <noneData game.properties: 158 bytes ui.properties: 83 bytes The game.properties and ui.properties files in the docs/user-guide/configmap/kubectl/ directory are represented in the data section of the ConfigMap. kubectl get configmaps game-config-2 -o yaml
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. Prevent issues from auto-closing with an comment. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale
/remove-lifecycle stale /assign

Discussion:
name: game-config namespace: default resourceVersion: "516" <del> selfLink: /api/v1/namespaces/default/configmaps/game-config-2 </del> <ins> selfLink: /api/v1/namespaces/default/configmaps/game-config </ins> uid: b4952dc3-d670-11e5-8cd0-68f728db1985 ```
Change:
This is a... [x] Feature Request [ ] Bug Report Study this topic and related topics: . Bring all of the etcd content into a coherent set of topics. Check for accuracy, and update as needed. Put topics into the appropriate templates. Edit topics to comply with our style guide.
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. Prevent issues from auto-closing with an comment. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale
Stale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten /remove-lifecycle stale
Rotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . Send feedback to sig-testing, kubernetes/test-infra and/or . /close
/remove-lifecycle rotten /lifecycle frozen /reopen
/language en
/priority backlog Is that OK?
Actually where exactly are the deviations from the style guide?
/triage accepted I don't see any obvious style concerns.
is wrong: you can't practice operating an etcd cluster for Kubernetes within a Katacoda playground, at least not unless you get very technical.
This issue has not been updated in over 1 year, and should be re-triaged. You can: Confirm that this issue is still relevant with (org members only) Close this issue with For more details on the triage process, see /remove-triage accepted
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details

Discussion:
## {{% heading "prerequisites" %}} <del> {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}} </del> <ins> You need to have a Kubernetes cluster, and the kubectl command-line tool must be configured to communicate with your cluster. It is recommended to run this task on a cluster with at least two nodes that are not acting as control plane nodes . If you do not already have a cluster, you can create one by using [minikube](https://minikube.sigs.k8s.io/docs/tutorials/multi_node/). </ins> <!-- steps -->
Change:
The URL can not access at the doc use the Go client library, and create a client using the rest.InClusterConfig() and kubernetes.NewForConfig()functions. They handle locating and authenticating to the apiserver. I think we should change this URL to
I can help fix it
This is fixed now and can be closed.

Discussion:
$ kubectl config view ``` <del> Many of the [examples](https://github.com/kubernetes/examples/tree/{{page.githubbranch}}/) provide an introduction to using kubectl and complete documentation is found in the [kubectl manual](/docs/user-guide/kubectl/index). </del> <ins> Many of the [examples](/docs/user-guide/kubectl-cheatsheet) provide an introduction to using kubectl and complete documentation is found in the [kubectl manual](/docs/user-guide/kubectl-overview). </ins> ### Directly accessing the REST API
Change:
This is a... <!-- choose one by changing [ ] to [x] --- [ ] Feature Request [x] Bug Report Problem: A DaemonSet by default tolerates not only node ready and node reachability taints. By design, it can tolerate memory pressure and disk pressure taints. For critical pods, it can tolerate outOfDisk taint as well. Proposed Solution: The above mentioned features should be documented. Page to Update:
/assign
Let the doc team know if you require any assistance from SMEs. Since you have assigned the defect to yourself, we assume that you have all the necessary information to fix this issue.
Thanks for the heads up. The source code (and comment) is already telling us what were missing.

Discussion:
- DaemonSet controller can make pods even when the scheduler has not been started, which can help cluster bootstrap. <del> Daemon pods do respect [taints and tolerations](/docs/concepts/configuration/assign-pod-node/#taints-and-tolerations-beta-feature), but they are created with `NoExecute` tolerations for the `node.alpha.kubernetes.io/notReady` and `node.alpha.kubernetes.io/unreachable` taints with no `tolerationSeconds`. This ensures that when the `TaintBasedEvictions` alpha feature is enabled, </del> <ins> Daemon pods do respect [taints and tolerations](/docs/concepts/configuration/assign-pod-node/#taints-and-tolerations-beta-feature), but they are created with `NoExecute` tolerations for the following taints with no `tolerationSeconds`: - `node.alpha.kubernetes.io/notReady` - `node.alpha.kubernetes.io/unreachable` - `node.alpha.kubernetes.io/memoryPressure` - `node.alpha.kubernetes.io/diskPressure` When the support to critical pods is enabled and the pods in a DaemonSet are labelled as critical, the Daemon pods are created with an additional `NoExecute` toleration for the `node.alpha.kubernetes.io/outOfDisk` taint with no `tolerationSeconds`. This ensures that when the `TaintBasedEvictions` alpha feature is enabled, </ins> they will not be evicted when there are node problems such as a network partition. (When the `TaintBasedEvictions` feature is not enabled, they are also not evicted in these scenarios, but due to hard-coded behavior of the NodeController rather than due to tolerations).
Change:
This is a... [x] Feature Request [ ] Bug Report Problem: From : We should document that K8s follows the international standard for punctuation inside quotes. For example, the American standard: the international standard: Proposed Solution: Add a page for punctuation to the .

Discussion:
<tr><td>Open the <code>/_data/concepts.yaml</code> file.</td><td>Open the /_data/concepts.yaml file.</td></tr> </table> <ins> ### Use the international standard for punctuation inside quotes <table> <tr><th>Do</th><th>Don't</th></tr> <tr><td>events are recorded with an associated "stage".</td><td>events are recorded with an associated "stage."</td></tr> <tr><td>The copy is called a "fork".</td><td>The copy is called a "fork."</td></tr> </table> </ins> ## Inline code formatting ### Use code style for inline code and commands