jiebi/CodeConvo huggingface dataset:
Code change:
Sebagai contoh, untuk menghasilan sebuah Secret dari _file-file_ `./username.txt` dan `./password.txt` ```shell <del> # Membuat sebuah file kustomization.yaml dengan SecretGenerator </del> <ins> # Membuat sebuah berkas kustomization.yaml dengan SecretGenerator </ins> cat <<EOF >./kustomization.yaml secretGenerator: - name: db-user-pass

Related discussion:
text: This issue is intended for contributor workshop as part of Cloud Native Day Indonesia on 7th Nov 2020. Please don't take it if you are not part of the workshop. There are several old translated pages that contain the english glossary "file", supposed to use Indonesian "berkas" as per KBBI. Please claim the task to fix them by giving comments on this Github issue. /language id Tasks to fix "file" -"berkas": [x] docs/tasks/manage-kubernetes-objects/imperative-[x] docs/tasks/manage-kubernetes-objects/declarative-[ ] docs/tasks/manage-kubernetes-objects/imperative-[ ] docs/tasks/configure-pod-container/configure-pod-[ ] docs/tasks/administer-cluster/sysctl-[ ] [x] [ ] docs/concepts/storage/storage-[ ] docs/concepts/services-networking/connect-applications-[ ] docs/concepts/services-[x] [x] docs/concepts/cluster-
/triage accepted
/assign
I'm taking this page docs/tasks/manage-kubernetes-objects/imperative-
/reopen
Reopened this issue. <detailsIn response to : /reopen Instructions 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
i'm taking this page docs/tasks/manage-kubernetes-objects/declarative-
may i change this file:
thanks feel free to raise the PR and link this issue
/reopen
Reopened this issue. <detailsIn response to : /reopen Instructions 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
I take this page :
please let me change another part. I will try to change this file
sure just mention this issue number when you raise the pull request /reopen
Reopened this issue. <detailsIn response to : please let me change another part sure just mention this issue number when you raise the pull request Instructions 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
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.
Code change:
Sebagai contoh, untuk menghasilan sebuah Secret dari _file-file_ `./username.txt` dan `./password.txt` ```shell <del> # Membuat sebuah file kustomization.yaml dengan SecretGenerator </del> <ins> # Membuat sebuah berkas kustomization.yaml dengan SecretGenerator </ins> cat <<EOF >./kustomization.yaml secretGenerator: - name: db-user-pass

Related discussion:
text: If this issue is safe to close now please do so with . Send feedback to sig-contributor-experience at . /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-contributor-experience at . /lifecycle rotten
Rotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . Send feedback to sig-contributor-experience at . /close
Closing this issue. <detailsIn response to : Rotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . /close Instructions 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
Code change:
The `dashboard` command enables the dashboard add-on and opens the proxy in the default web browser. You can create Kubernetes resources on the dashboard such as Deployment and Service. <del> If you are running in an environment as root, see [Open Dashboard with URL](#open-dashboard-with-url). </del> <ins> To find out how to avoid directly invoking the browser from the terminal and get a URL for the web dashboard, see the "URL copy and paste" tab. </ins> By default, the dashboard is only accessible from within the internal Kubernetes virtual network. The `dashboard` command creates a temporary proxy to make the dashboard accessible from outside the Kubernetes virtual network.

Related discussion:
text: This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: The page has a broken link / anchor named "Open Dashboard with URL" in the Dashboard section. The markdown anchor named #open-dashboard-with-url cannot be resolved. Proposed Solution: This link / anchor needs to be fixed, however I am not able to understand what section it referred to in the first place. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/language en /sig docs
Page related to the issue:
I think the URL should be replaced with
Let's wait for the opinions of other members regarding the same.
I would to like to work on this issue is the triage gets accepted.
Thanks. I checked further. Please check . Here you will find the section for the "Open Dashboard with URL". It seems this section was removed in later versions of this page, but the anchor/link was not removed.
The anchor for "Open Dashboard with URL," , is now obsolete as we've integrated this content into tab layout (Launch a browser, URL copy and paste) on the.
Pull request has been submitted quite some time ago to handle this issue, and it's awaiting review and approval for merging.
Indeed. Once is approved, it will address this issue. I do not see anyone actively working on this PR since many days. has volunteered to help. please take a look at There are some suggestions from in the PR already.
/triage accepted
Code change:
# Replace the value of "containerRuntimeEndpoint" for a different container runtime if needed. ``` --> ```sh cat << EOF > /etc/systemd/system/kubelet.service.d/kubelet.conf # 将下面的 "systemd" 替换为你的容器运行时所使用的 cgroup 驱动。

Related discussion:
text: apiVersion: kind: KubeletConfiguration authentication: anonymous: enabled: false webhook: enabled: false authorization: mode: AlwaysAllow apiVersion: kind: KubeletConfiguration authentication: anonymous: enabled: false webhook: enabled: false authorization: mode: AlwaysAllow
Use kubeadm to create a highly available etcd cluster apiVersion: kind: KubeletConfiguration authentication: anonymous: enabled: false webhook: enabled: false authorization: mode: AlwaysAllow There is a problem here, there is no indentation Normal should be apiVersion: kind: KubeletConfiguration authentication: anonymous: enabled: false webhook: enabled: false authorization: mode: AlwaysAllow
provide more details of the issue as it's difficult to address your issue with the information that you have provided. Atleast mention the page you are referring to. /triage needs-information
Page related to the issue :
/language zh
/retitle The YAML format may be not correct in setup-ha-etcd-with-kubeadm
/triage accepted /assign
Code change:
## {{% heading "prerequisites" %}} <del> You must use a kubectl version that is within one minor version difference of your cluster. For example, a v1.2 client should work with v1.1, v1.2, and v1.3 master. </del> <ins> You must use a kubectl version that is within one minor version difference of your cluster. For example, a v{{< skew latestVersion >}} client can communicate with v{{< skew prevMinorVersion >}}, v{{< skew latestVersion >}}, and v{{< skew nextMinorVersion >}} control planes. </ins> Using the latest version of kubectl helps avoid unforeseen issues. ## Install kubectl on macOS

Related discussion:
text: This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: There are a couple of issues with existing wording: “master” should be read “control plane” versions aren't current. Proposed Solution: Replace that text with: Page to Update: Additional Information: /language en /kind bug /wg naming
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
/help If you're picking this up and want to be extra neat, replace those specific version numbers with shortcodes that automatically fill in based on the current release; for example:
This request has been marked as needing help from a contributor. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /help </details
/assign
Code change:
<!-- overview --> <del> If you want to control traffic flow at the IP address or port level (OSI layer 3 or 4), then you might consider using Kubernetes NetworkPolicies for particular applications in your cluster.  NetworkPolicies are an application-centric construct which allow you to specify how a {{< glossary_tooltip text="pod" term_id="pod">}} is allowed to communicate with various network "entities" (we use the word "entity" here to avoid overloading the more common terms such as "endpoints" and "services", which have specific Kubernetes connotations) over the network. </del> <ins> If you want to control traffic flow at the IP address or port level (OSI layer 3 or 4), then you might consider using Kubernetes NetworkPolicies for particular applications in your cluster.  NetworkPolicies are an application-centric construct which allow you to specify how a {{< glossary_tooltip text="pod" term_id="pod">}} is allowed to communicate with various network "entities" (we use the word "entity" here to avoid overloading the more common terms such as "endpoints" and "services", which have specific Kubernetes connotations) over the network. NetworkPolicies apply to a connection with a pod on one or both ends, and are not relevant to other connections. </ins> The entities that a Pod can communicate with are identified through a combination of the following 3 identifiers:

Related discussion:
text: As discussed in the sig-networking mailing list (), has not been fully updated since the introduction of egress filtering.
/sig network /sig docs /kind bug (it's a bug because the doc should already have been updated) /language en /triage accepted
/priority backlog
Code change:
<!-- overview --> {{< glossary_definition term_id="etcd" length="all" >}} ## {{% heading "prerequisites" %}} {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}

Related discussion:
text: " etcd "client.cert " etcd etcd " " etcd client.key etcd "
~ GitHub is not the right place for support requests.~ ~If you're looking for help, oyu could ask on .~ ~You can also post your question on the or the forum. There are other support venues with contributions from the wider community of Kubernetes users.~
/triage accepted /kind bug
/remove-kind support
Thanks
/language zh
/priority backlog
Code change:
* For detailed information about Pod and container status in the API, see the API reference documentation covering <del> [`status`](/docs/reference/kubernetes-api/workload-resources/pod-v1/#PodStatus) for Pod. </del>  No newline at end of file <ins> [`status`](/docs/reference/kubernetes-api/workload-resources/pod-v1/#PodStatus) for Pod. </ins>

Related discussion:
text: This is a Bug Report Problem: An explanation in the Pod phase section is misleading. A pod doesn't have a state until it is configured not to be restarted. If the is not set, the pod will still be in the state. Proposed Solution: All containers in the Pod have terminated, and at least one container has terminated in failure. That is, the container either exited with non-zero status or was terminated by the system, and will not be restarted. Page to Update: Kubernetes Version: v1.30.1 I'll be happy to work on it if it's 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
/language en /sig docs
/sig node
so long as you're confident your understanding is correct, you don't need anyone to tell you it's OK to start work. Kubernetes is open source.
That’s true, thanks. /assign
Code change:
This feature gate will never graduate to beta or stable. - `TopologyManagerPolicyBetaOptions`: Allow fine-tuning of topology manager policies, experimental, Beta-quality options. <del> This feature gate guards *a group* of topology manager options whose quality level is alpha. </del> <ins> This feature gate guards *a group* of topology manager options whose quality level is beta. </ins> This feature gate will never graduate to stable. - `TopologyManagerPolicyOptions`: Allow fine-tuning of topology manager policies, - `UserNamespacesStatelessPodsSupport`: Enable user namespace support for stateless Pods.

Related discussion:
text: This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: Typo in "Feature Gates" page cf. Proposed Solution: In , replace with . Page to Update: ,alpha,-.%20This%20feature%20gate%20will%20never%20graduate%20to%20stable <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/assign
/triage accepted
Hi could you provide an update on the progress of this issue? I'm particularly interested in knowing what the current status is and if I can carry on this issue.
, I will submit a PR today .
/close
Closing this issue. <detailsIn response to : /close </details
Code change:
*  The named groups are at REST path `/apis/$GROUP_NAME/$VERSION` and use `apiVersion: $GROUP_NAME/$VERSION` (for example, `apiVersion: batch/v1`). You can find the full list of supported API groups in <del> [Kubernetes API reference](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/). </del> <ins> [Kubernetes API reference](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#-strong-api-groups-strong-). </ins> ## Enabling or disabling API groups   {#enabling-or-disabling} Certain resources and API groups are enabled by default. You can enable or disable them by setting `--runtime-config` on the API server.  The <del> `--runtime-config` flag accepts comma separated `<key>=<value>` pairs describing the runtime configuration of the API server. For example: </del> <ins> `--runtime-config` flag accepts comma separated `<key>[=<value>]` pairs describing the runtime configuration of the API server. If the `=<value>` part is omitted, it is treated as if `=true` is specified. For example: </ins> - to disable `batch/v1`, set `--runtime-config=batch/v1=false` - to enable `batch/v2alpha1`, set `--runtime-config=batch/v2alpha1`

Related discussion:
text: 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
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. 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 A possible solution is to have the doc generator summarizes the API groups it identified. The generator can put that into a separate section in the API reference doc generated.
/lifecycle frozen
It would be great to have it documented under which API resources lie within a specific version - something like
Is there any default value in --runtime-config? for example,it is all work file when I config '--runtime-, ' or '--runtime-config="" ' in kube-apiserver. so I was confused, how can I know which api support by default?
/kind feature /priority backlog
Another gotcha with the current documentation: it mentions that takes a "A set of key=value pairs" - but what is the syntax for that set? Comma-separated? Space-separated? JSON map? I had to google, which led me to this issue here.
/triage accepted
/sig api-machinery I think
Code change:
/docs/tasks/administer-cluster/quota-memory-cpu-namespace/     /docs/tasks/administer-cluster/manage-resources/quota-memory-cpu-namespace/ 301 /docs/tasks/administer-cluster/quota-pod-namespace/     /docs/tasks/administer-cluster/manage-resources/quota-pod-namespace/ 301 /docs/tasks/administer-cluster/reserve-compute-resources/out-of-resource.md     /docs/tasks/administer-cluster/out-of-resource/ 301 <del> /docs/tasks/administer-cluster/out-of-resource/     /docs/concepts/scheduling-eviction/pod-eviction/ 301 </del> <ins> /docs/tasks/administer-cluster/out-of-resource/     /docs/concepts/scheduling-eviction/node-pressure-eviction/ 301 </ins> /docs/tasks/administer-cluster/romana-network-policy/     /docs/tasks/administer-cluster/network-policy-provider/romana-network-policy/ 301 /docs/tasks/administer-cluster/running-cloud-controller.md     /docs/tasks/administer-cluster/running-cloud-controller/ 301 /docs/tasks/administer-cluster/share-configuration/     /docs/tasks/access-application-cluster/configure-access-multiple-clusters/ 301

Related discussion:
text: A on is broken and returning 404 page.
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
Code change:
<ins> apiVersion: v1 kind: Pod metadata: name: dapi-test-pod spec: containers: - name: test-container image: k8s.gcr.io/busybox command: [ "/bin/sh", "-c", "env" ] envFrom: - configMapRef: name: special-config restartPolicy: Never </ins>

Related discussion:
text: This is a Feature Request <!-- Please only use this template for submitting feature/enhancement requests --<!-- See for guidance on writing an actionable issue description. --What would you like to be Translate tasks/configure-pod-container/configure-pod-configmap/ into Japanese. Why is this needed This page has not been translated. Comments /language ja
/assign
/close
Closing this issue. <detailsIn response to : /close Instructions 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
Code change:
<p>If you haven't worked through the earlier sections, start from <a href="/docs/tutorials/kubernetes-basics/create-cluster/cluster-intro/">Using minikube to create a cluster</a>.</p> <p><em>Scaling</em> is accomplished by changing the number of replicas in a Deployment</p> <del> <p><b>NOTE</b> If you are trying this after <a href="/docs/tutorials/kubernetes-basics/expose/expose-intro/">the previous section </a>, then you may have deleted the service you created, or have created a Service of <tt>type: NodePort</tt>. In this section, it is assumed that a service with <tt>type: LoadBalancer</tt> is created for the kubernetes-bootcamp Deployment.</p> <p>If you have <em>not</em> deleted the Service created in <a href="/docs/tutorials/kubernetes-basics/expose/expose-intro">the previous section</a>, first delete that Service and then run the following command to create a new Service with its <tt>type</tt> set to <tt>LoadBalancer</tt>:</p> <p><code><b>kubectl expose deployment/kubernetes-bootcamp --type="LoadBalancer" --port 8080</b></code></p> </del> </br> </div> <div class="col-md-4">

Related discussion:
text: I find this small bit in the scale-intro a bit confusing: and then directly under that paragraph, there is this highlighted "Note" section, that states: TL;DR; Paragraph instructs me to delete the "NodePort" service, because this sections expects a "Loadbalancer" service to be active. Highlighted Note instructs me to re-create the "NodePort" service after the "Loadbalancer" service was created.
Page reported in issue (based on the issue title): /language en
/retitle Conflicting guidance regarding Service creation in "Scale Your App" tutorial /kind bug
Removing this ambiguity will improve the tutorial's usability. /priority backlog /triage accepted
I will try to help with this. /assign
Code change:
### Check the local DNS configuration first Take a look inside the resolv.conf file. <del> (See [Inheriting DNS from the node](/docs/tasks/administer-cluster/dns-custom-nameservers/#inheriting-dns-from-the-node) and </del> <ins> (See [Customizing DNS Service](/docs/tasks/administer-cluster/dns-custom-nameservers) and </ins> [Known issues](#known-issues) below for more information) ```shell

Related discussion:
text: says: Pod's DNS Policy : The Pod inherits the name resolution configuration from the node that the pods run on. See related discussion for more details. “Related discussion” is a hyperlink to : Any DNS query that does not match the configured cluster domain suffix, such as "", is forwarded to the upstream nameserver inherited from the node. Cluster administrators may have extra stub-domain and upstream DNS servers configured. See related discussion for details on how DNS queries are handled in those cases. “Related discussion” is a hyperlink to Both hyper targets do not exist in the destination webpage (so that the browser scrolls to the right place). contains a hyperlink “See Inheriting DNS from the node” → , which as above does not exist.
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
/assign
/sig docs