jiebi/CodeConvo huggingface dataset:
Change:
In concept docs (): but in API docs (): It's also a bit unclear what "primary IP family" means. My first thought was the primary IP family is what's used for (as opposed to which includes all IP families, not just the primary). Is that interpretation correct? If so, it might be better to avoid that terminology because there's also this text in the concept docs which makes "primary" overloaded:
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. 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
/sig docs /sig network
What i have to do in this issue?
The "conditionally mutable" part is correct; that was later and we must have missed updating some places. Yes "Primary/secondary IP family" is widely used. If you think it's confusing then the "primary/secondary field" wording should be changed, not the "primary/secondary IP family". Though really, "primary/secondary IP family" is not really that relevant in the context of individual services... the cluster as a whole has a primary service IP family, which is the family that will get assigned to single-stack services that don't explicitly request an IP family. But for services that request dual-stack, the only difference between "IPv4-primary" and "IPv6-primary" is the fact that old pre-dual-stack clients might treat them as single-stack of that family.
In the Service API docs, I think "primary IP family" is referring to the first family in the list, which may or may not be the same as the cluster's primary service IP family. Maybe we can use "first" and "second" IP families in the context of individual services:
This is feedback on documentation. I think is the page that should change. /transfer website
We might also want to reword: however, the focus of this issue is removing an inconsistency.
/assign
/triage accepted Let's make this clearer.
/unassign This issue is open to work on. Feel free to assign.
/assign

Discussion:
`.spec.ipFamilies`, on the Service. {{< note >}} <del> The `.spec.ipFamilies` field is immutable because the `.spec.ClusterIP` cannot be reallocated on a Service that already exists. If you want to change `.spec.ipFamilies`, delete and recreate the Service. </del> <ins> The `.spec.ipFamilies` field is conditionally mutable: you can add or remove a secondary IP address family, but you cannot change the primary IP address family of an existing Service. </ins> {{< /note >}} You can set `.spec.ipFamilies` to any of the following array values:
Change:
The "Using environment variables inside of your config" feature is great and has been very useful. Thanks! I have two minor suggestions: would also be useful to document which fields of a container spec this interpolation applies (or if it applies to almost all fields, what the exceptions are.) , the example is slightly confusing / misleading. The key feature that is documented here is the ability to statically use env vars defined in the config in other config fields. While the example is calling with a single string, it may look at a glance like a shell command which would do the interpolation itself (note notation and not or ). Perhaps a clearer example would be using env vars inside of other env vars: This shows more clearly that environment variable is configured statically from previously set environment variables - before the Pod is created, no shell interpolation involved.
/triage accepted /language en
/assign
As per my understanding, you are expecting here to add where this environment variable applies inside the configuration file like below. To set environment variables, include the env or envFrom field in the configuration file under .spec.containers[*]. Please confirm if i wrongly understood.
PR Raised here .

Discussion:
## Using environment variables inside of your config <del> Environment variables that you define in a Pod's configuration can be used elsewhere in the configuration, for example in commands and arguments that you set for the Pod's containers. </del> <ins> Environment variables that you define in a Pod's configuration under `.spec.containers[*].env[*]` can be used elsewhere in the configuration, for example in commands and arguments that you set for the Pod's containers. </ins> In the example configuration below, the `GREETING`, `HONORIFIC`, and `NAME` environment variables are set to `Warm greetings to`, `The Most <del> Honorable`, and `Kubernetes`, respectively. Those environment variables are then used in the CLI arguments passed to the `env-print-demo` container. </del> <ins> Honorable`, and `Kubernetes`, respectively. The environment variable `MESSAGE` combines the set of all these environment variables and then uses it as a CLI argument passed to the `env-print-demo` container. </ins> ```yaml apiVersion: v1

value: "The Most Honorable" - name: NAME value: "Kubernetes" <ins> - name: MESSAGE value: "$(GREETING) $(HONORIFIC) $(NAME)" </ins> command: ["echo"] <del> args: ["$(GREETING) $(HONORIFIC) $(NAME)"] </del> <ins> args: ["$(MESSAGE)"] </ins> ``` Upon creation, the command `echo Warm greetings to The Most Honorable Kubernetes` is run on the container.
Change:
This is a Bug Report Problem: Link for AppArmorProfile in is broken. Proposed Solution: Should be updated with correct link Page to Update:
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
/area blog /language en
/assign

Discussion:
### AppArmor support This version introduces the initial support for AppArmor, allowing users to load and <del> unload AppArmor profiles into cluster nodes by using the new [AppArmorProfile](https://github.com/kubernetes-sigs/security-profiles-operator/blob/main/deploy/base/crds/apparmorprofile.yaml) CRD. </del> <ins> unload AppArmor profiles into cluster nodes by using the new [AppArmorProfile](https://github.com/kubernetes-sigs/security-profiles-operator/blob/main/deploy/base-crds/crds/apparmorprofile.yaml) CRD. </ins> To enable AppArmor support use the [enableAppArmor feature gate](https://github.com/kubernetes-sigs/security-profiles-operator/blob/main/examples/config.yaml#L10) switch of your SPO configuration. Then use our [apparmor example](https://github.com/kubernetes-sigs/security-profiles-operator/blob/main/examples/apparmorprofile.yaml) to deploy your first profile across your cluster.
Change:
This is a Feature Request What would you like to be Localize to Spanish Why is this needed Comments
/triage accepted
/language es
/kind feature
/assign
/assign

Discussion:
<ins> --- title: Container Runtime Interface (CRI) content_type: concept weight: 60 --- <!-- overview --> _CRI_ es una interfaz de plugin que permite que kubelet use una amplia variedad de container runtimes, sin necesidad de volver a compilar los componentes del clúster. Necesitas un _{{<glossary_tooltip text="container runtime" term_id="container-runtime">}}_ ejecutándose en cada Nodo en tu clúster, de manera que {{<glossary_tooltip text="kubelet" term_id="kubelet">}} pueda iniciar los {{<glossary_tooltip text="Pods" term_id="pod">}} y sus contenedores. {{<glossary_definition prepend="Container Runtime Interface (CRI) es" term_id="container-runtime-interface" length="all">}} <!-- body --> ## API {#api} {{< feature-state for_k8s_version="v1.23" state="stable" >}} Kubelet actúa como un cliente cuando se conecta al _runtime_ del contenedor a través de gRPC. El _runtime_ y los _endpoints_ del servicio de imágenes deben estar disponibles en el _runtime_ del contenedor, que se puede configurar por separado dentro del kubelet usando `--image-service-endpoint` [banderas de línea de comando](/docs/reference/command-line-tools-reference/kubelet). Para Kubernetes v{{< skew currentVersion >}}, kubelet prefiere usar CRI `v1`. Si el _runtime_ del contenedor no es compatible con `v1` del CRI, kubelet intenta negociar cualquier versión compatible anterior. El kubelet v{{< skew currentVersion >}} también puede negociar CRI `v1alpha2`, pero esta versión se considera obsoleta. Si el kubelet no puede negociar una versión CRI soportada, el kubelet se da por vencido y no se registra como un nodo. ## Actualizando Al actualizar Kubernetes, el kubelet intenta seleccionar automáticamente la última versión de CRI al reiniciar el componente. Si eso falla, entonces la alternativa se llevará a cabo como se mencionó anteriormente. Si se requirió una rellamada de gRPC porque el _runtime_ del contenedor se ha actualizado, entonces el _runtime_ del contenedor también debe soportar la versión seleccionada inicialmente o se espera que la rellamada falle. Esto requiere un reinicio del kubelet. ## {{% heading "whatsnext" %}} - Más información sobre CRI [definición de protocolo](https://github.com/kubernetes/cri-api/blob/c75ef5b/pkg/apis/runtime/v1/api.proto) </ins>
Change:
This is a Bug Report While applying written in is triggering an error Whereas by removing the labels from the and Applying the kustomization directory to create the ConfigMap object get created successfully. <!--Required Information--Problem: cat <<EOF Here is the configmap created previously. Proposed Solution: Update it with suitable answer. Refer : for kustomization update. Page to Update:
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
/sig docs /language en
The unknown field was in this commit and it was not supported refer to the code We can add labels via refer to I can help open a PR to update the code sections.

Discussion:
cat <<EOF >./kustomization.yaml configMapGenerator: - name: game-config-4 <del> labels: game-config: config-4 </del> <ins> options: labels: game-config: config-4 </ins> files: - configure-pod-container/configmap/game.properties EOF

cat <<EOF >./kustomization.yaml configMapGenerator: - name: game-config-5 <del> labels: game-config: config-5 </del> <ins> options: labels: game-config: config-5 </ins> files: - game-special-key=configure-pod-container/configmap/game.properties EOF
Change:
This is a Feature Request What would you like to be Localize to Spanish Why is this needed Comments /triage accepted /language es /kind feature /sig docs
/assign

Discussion:
<ins> --- title: Container Runtime Interface id: container-runtime-interface date: 2021-11-24 full_link: /docs/concepts/architecture/cri short_description: > El protocolo principal para la comunicación entre el kubelet y el Container Runtime. aka: tags: - cri --- El protocolo principal para la comunicación entre el _kubelet_ y el _Container Runtime_. <!--more--> La _Kubernetes Container Runtime Interface_ (CRI) define el principal protocolo de [gRPC](https://grpc.io) para la comunicación entre los [componentes de clúster](/docs/concepts/overview/components/#componentes-de-nodo) _{{<glossary_tooltip text="kubelet" term_id="kubelet">}}_ y _{{<glossary_tooltip text="container runtime" term_id="container-runtime">}}_. </ins>
Change:
!
url Language Chinese
/retitle [zh-cn] Disorganized Layout of 'Kubernetes Components Page' /language zh
/triage accepted /kind bug
/assign

Discussion:
<!-- overview --> <!-- When you deploy Kubernetes, you get a cluster. <del> {{< glossary_definition term_id="cluster" length="all" prepend="A Kubernetes cluster consists of">}} </del> <ins> {{ < glossary_definition term_id="cluster" length="all" prepend="A Kubernetes cluster consists of">}} </ins> This document outlines the various components you need to have for a complete and working Kubernetes cluster. <del> {{< figure src="/images/docs/components-of-kubernetes.svg" alt="Components of Kubernetes" caption="The components of a Kubernetes cluster" class="diagram-large" >}} </del> <ins> {{ < figure src="/images/docs/components-of-kubernetes.svg" alt="Components of Kubernetes" caption="The components of a Kubernetes cluster" class="diagram-large" >}} </ins> --> 当你部署完 Kubernetes，便拥有了一个完整的集群。
Change:
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: It failed when running the command in the doc It works after replacing the first with in Proposed Solution: Replace the first with in Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
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
I will open a PR to fix it.
/retitle Incorrect git clone URL in "Opening a pull request" page /language en

Discussion:
1. In a terminal window, clone your fork and update the [Docsy Hugo theme](https://github.com/google/docsy#readme): ```shell <del> git clone git@github.com/<github_username>/website </del> <ins> git clone git@github.com:<github_username>/website </ins> cd website git submodule update --init --recursive --depth 1 ```
Change:
Parent issue: Replace the deprecated shortcode with the shortcode in the Brazilian Portuguese localized docs. /assign /triage accepted /language pt

Discussion:
``` Serviços possuem endereço IP dedicado e são disponibilizados para o contêiner via DNS, <del> se possuírem [DNS addon](https://releases.k8s.io/{{< param "fullversion" >}}/cluster/addons/dns/) habilitado. </del> <ins> se possuírem [DNS addon](https://releases.k8s.io/v{{< skew currentPatchVersion >}}/cluster/addons/dns/) habilitado. </ins>

## Requisitos de plugins de Rede <del> Além de prover a [interface `NetworkPlugin`](https://github.com/kubernetes/kubernetes/tree/{{< param "fullversion" >}}/pkg/kubelet/dockershim/network/plugins.go) </del> <ins> Além de prover a [interface `NetworkPlugin`](https://github.com/kubernetes/kubernetes/tree/v{{< skew currentPatchVersion >}}/pkg/kubelet/dockershim/network/plugins.go) </ins> para configuração da rede do pod, o plugin pode necessitar de suporte específico ao kube-proxy. O proxy iptables obviamente depende do iptables, e o plugin deve garantir que o

{{< note >}} Para fazer o download de uma versão específica, substitua a parte `$(curl -L -s https://dl.k8s.io/release/stable.txt)` do comando pela versão específica. <del> Por exemplo, para fazer download da versão {{< param "fullversion" >}} no Linux, digite: </del> <ins> Por exemplo, para fazer download da versão {{< skew currentPatchVersion >}} no Linux, digite: </ins> ```bash <del> curl -LO https://dl.k8s.io/release/{{< param "fullversion" >}}/bin/linux/amd64/kubectl </del> <ins> curl -LO https://dl.k8s.io/release/v{{< skew currentPatchVersion >}}/bin/linux/amd64/kubectl </ins> ``` {{< /note >}}
Change:
<img width="1077" alt="Screenshot 2023-05-10 at 1 12 29 PM" src=""Please update the details as per (GKE 1.17 and later) (versions earlier than 1.17)
Page related to the issue: /retitle Update Internal Load Balancer annotation for GCP in accordance with Google Cloud Kubernetes Engine doc /language en
/triage accepted
/assign

Discussion:
metadata: name: my-service annotations: <del> cloud.google.com/load-balancer-type: "Internal" </del> <ins> networking.gke.io/load-balancer-type: "Internal" </ins> [...] ```
Change:
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 still references to instead of is the correct advertised download host and will eventually move to be fastly shielding a fully community-owned bucket ref: Proposed Solution: Replace with Also replace any references with using if applicable. Page to Update: Assorted e.g. , <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
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
hi Not a problem, didn't see anyone assigned to this issue. I am unassigning myself and assigning it to you. /unassign
/assign
Hi, I found a small issue with your proposed changes regarding one of the URLs, which is mentioned twice in the file. While returns as expected, I am getting an nginx-rendered HTML page saying for the new command () instead. As I understand, it happens due to the redirect configured on the new web server. Thus, works fine for me (it returns as expected).
i see Let me update it, thanks your work
Just done, please review all of PRs
Thanks!
And yes: These will need to follow redirects, in the future the tentative plan is it will redirect to a CDN in front of a different bucket created in a fully project / SIG-K8s-Infra controlled GCP or AWS account. I would recommend for downloading with curl more generally, even in docs / usage for other hosts.

Discussion:
When that’s looking good we’re able to access the master node of the Kubernetes cluster with kubectl. Kubectl for ARM can be downloaded from googleapis storage. kubectl get nodes shows which cluster nodes are registered with its status. The master node is named 127.0.0.1. ``` <del> $ curl -fsSL -o /usr/bin/kubectl https://storage.googleapis.com/kubernetes-release/release/v1.1.2/bin/linux/arm/kubectl </del> <ins> $ curl -fsSL -o /usr/bin/kubectl https://dl.k8s.io/release/v1.1.2/bin/linux/arm/kubectl </ins> $ kubectl get nodes

The recommended way to install it on Linux is to download the pre-built binary and move it to a directory under the `$PATH`. ```shell <del> curl -LO https://storage.googleapis.com/kubernetes-release/release/$(curl -s https://storage.googleapis.com/kubernetes-release/release/stable.txt)/bin/linux/amd64/kubectl  </del> <ins> curl -LO https://dl.k8s.io/release/$(curl -L -s https://dl.k8s.io/release/stable.txt)/bin/linux/amd64/kubectl  </ins> && sudo install kubectl /usr/local/bin && rm kubectl ```
Change:
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 still references to instead of is the correct advertised download host and will eventually move to be fastly shielding a fully community-owned bucket ref: Proposed Solution: Replace with Also replace any references with using if applicable. Page to Update: Assorted e.g. , <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
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
hi Not a problem, didn't see anyone assigned to this issue. I am unassigning myself and assigning it to you. /unassign
/assign
Hi, I found a small issue with your proposed changes regarding one of the URLs, which is mentioned twice in the file. While returns as expected, I am getting an nginx-rendered HTML page saying for the new command () instead. As I understand, it happens due to the redirect configured on the new web server. Thus, works fine for me (it returns as expected).
i see Let me update it, thanks your work
Just done, please review all of PRs
Thanks!
And yes: These will need to follow redirects, in the future the tentative plan is it will redirect to a CDN in front of a different bucket created in a fully project / SIG-K8s-Infra controlled GCP or AWS account. I would recommend for downloading with curl more generally, even in docs / usage for other hosts.

Discussion:
RELEASE="$(curl -sSL https://dl.k8s.io/release/stable.txt)" ARCH="amd64" cd $DOWNLOAD_DIR <del> sudo curl -L --remote-name-all https://storage.googleapis.com/kubernetes-release/release/${RELEASE}/bin/linux/${ARCH}/{kubeadm,kubelet,kubectl} </del> <ins> sudo curl -L --remote-name-all https://dl.k8s.io/release/${RELEASE}/bin/linux/${ARCH}/{kubeadm,kubelet,kubectl} </ins> sudo chmod +x {kubeadm,kubelet,kubectl} RELEASE_VERSION="v0.4.0"