Question:
 <?xml version="1.0" encoding="UTF-8"?>  <!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd"> <svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" version="1.1" width="809px" height="638px" viewBox="-0.5 -0.5 809 638" content="<mxfile host="app.diagrams.net" modified="2023-09-22T08:57:24.261Z" agent="Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36" etag="EPPLAoCIsPnsc_DPojmh" version="21.8.0" type="device"><diagram name="Page-1" id="2_0QGAMlV9SS6-_4G6dn">7ZxZc6M4EIB/jR/jAnE/ZnLt1OyRrVTtTPYlRUC22cHIKyCx99dvCyRzKTFOwMaHpyoDjSSg+1Oru8EeaVfz5R11F7PfiI/DEVL85Ui7HiGETAP+MsEqF5i2kwumNPBzkVoIHoL/MBcqXJoGPo4rDRNCwiRYVIUeiSLsJRWZSyl5rTabkLB61oU7xQ3Bg+eGTen3wE9mXKqaTnHgFxxMZ/zUNrLyA8+u93NKSRrx80UkwvmRuSuG4fcYz1yfvJZE2s1Iu6KEJPnWfHmFQ6ZVobG83+0bR9eXTHGUtOkwmeNfo9uHby+Gvnh6Sp/+NP75+4KP8uKGKVcFv9hkJXRDZ2T+nIKCv7zOggQ/LFyPHXkFEEA2S+Yh7Kmw6YbBNIJtDy4IUxBMgjC8IiGh2UCahsyrGxPkcULJTyyOZCqDxiRKSo0n2WfdWFhFHRsga966uA9ME7wsibgq7jCZ44SuoIlAVlGtMaeWQ4ssbqnXAgFN57JZyfqqwYUux266Hr7QP2xwE2xhDiQxhxkmXD3MLmLqmP+mDJwvarGZzQ+hwEIoVFluV5i3EJa2pvz/7MzP0vbsei7yq7mEBqq9WEpHebx5EAOBRp7rg4MsvzMhrsEHOgMfgDfDV2NNN9i/GlY+nrhpdlopgTLSFpgGYFpM2ZmDaAoHFBnqHRCpappS4dFu4qhqRhNHpy8a9VN1DqphVE1h7N0zGBs9w4en6B3JltsRWz/Escv7r7B/s0xwFAckiiu9Ws3cbFHEPp8w283e2+zTgAGOKNmnR8sju7Es6E3jrxf1svHNvmxv9mf7a2b2FUnZ7bnZWBkIru/DX1BjQHHI1BPhV3ZstYAojbdJZhDpKN/SZ0wj8JBMzqjRbtsSAiZJqhjI536JDS4SziTEEzYCM28AwdwlF88D3w/fWjOqXLIL5OGoajYdzRrELtAydXusahW2HGNsak0vr2tjS+LoDXst7pwx6+gij9//2GvgsXEdq0cj3Ye4KqoHFGNFcUqfPccXdh9+rS2J7/o/isEmgcf2YSy49TQhkNAxJ5O5Q+wH7NgkwKHPHF8QsasFtaw7ZHefr6K51zxsv9hJxuWgsa1WiNSQZG2FxEx1JN6vLwydo3N9+066Pun7esmubLPqDCGU3LP7E8Wv9/IrHPmXrL5VqLGk/uqUxcsg+cGPsO1HJs/0yfaul6Vm1yu+86ZiY5JSD2+eNNivFNaa6i9p15DEzEIGYSa415dqOU6mcX6GexJkU3PtW5SadfVaoJTfEO9WrpI1RkIbRkpcOsVJY6QMgfWNf4KKzTWgHjK9S8/DcXyaKZ/dqATqknx/tymfyBOOaFEaYjwuQ0q+TvURj8sw2/ESdLIlPkn939h//V/tpczXSUrkzdxoyvKbvO7DPD0NV6wkDvc0X4R4DsaANZywVIhM1g2f0yBMLrIE6ZwOVQC0q97AlOVCOhrLCkG98be51Hhoy845F5JEPLWFyNx/LnSuPw6Lu048nFFfYi1z76DJio4nEfGoViPisbT9RzzHV307T3xUC232P+2RrNZ22JidAxvJexs2GtyKs76NQeV0JCnndH+RMJ2zR/hwi8oDpi+BJ/a+RlOK41js3mMaB3ECNhJ9Tj6TUy3HHKMadpJaAjLkj/Wt3sjbcSn5azShLpg09ZKU4pOpHxt6dbVzJNnUbqvHaHP1uNtnCPzxOKv9nIbRQUHG0Izeopbb8+NE0Cdd/cgaKkgVAt5TsYSg6Jztid6tjSh63ouXc0effZrJNZU/2nunHVfxQJ56qrZV9TxIqcHV9qln44VXVauN1PNTTyQrPH4C3gJEo4yhugFBAX0B+mOZcyn022D7cUKNloSiYRO6fuFna0KdWs2yETb1TaisQtkJoY6Daq6yLaVbuOa3Ke3YlVrH4UoPGNQWFc6Dc6Uf51F8nXATj9aZx554lFV4D4PHT1CntcROHTZ2ut4Vdlq9wNYzdiKAPS3s9LbYaWfueuKuxVeqj4+7tgn0sF4bPibsUF/YKeArKumJ7jgt4du6dtRdGiLeZNrsCQeeiBwwkrIq9CeQlHu0saKYbYuSW3vQDnm02/JoDptH0+6KR3PHNUat4wL5QazM4h43Fw6VM3c9cSd7qfvouWudAA+88HLA3PX2TMVx6g/3DiAgdNoCOayAsAgAxbf41V0DCYS4q1KzBWsQb3PJivHulTU6mHqlA2zk19Dt/OirUN7/3NiFXx5Wql78DI944aIO7/CmATLll/zmNKh3qM2bbacB7BY/L5g3L369Ubv5Hw==</diagram></mxfile>" style="background-color: rgb(255, 255, 255);"><defs/><g><path d="M 630.35 154 L 749.35 206.5 L 630.35 259 L 511.35 206.5 Z" fill="#326ce6" stroke="none" pointer-events="all"/><ellipse cx="77.35" cy="52.5" rx="47.25" ry="31.499999999999996" fill="#454545" stroke="none" pointer-events="all"/><g transform="translate(-0.5 -0.5)scale(0.7)"><switch><foreignObject pointer-events="none" width="143%" height="143%" requiredFeatures="http://www.w3.org/TR/SVG11/feature#Extensibility" style="overflow: visible; text-align: left;">

YES

</foreignObject><text x="111" y="79" fill="rgb(0, 0, 0)" font-family="Helvetica" font-size="12px" text-anchor="middle">YES</text></switch></g><path d="M 303.1 0 L 422.1 52.5 L 303.1 105 L 184.1 52.5 Z" fill="#326ce6" stroke="none" pointer-events="all"/><rect x="0.35" y="133" width="154" height="42" fill="#ffffff" stroke="#000000" stroke-width="1.05" pointer-events="all"/><g transform="translate(-0.5 -0.5)scale(0.7)"><switch><foreignObject pointer-events="none" width="143%" height="143%" requiredFeatures="http://www.w3.org/TR/SVG11/feature#Extensibility" style="overflow: visible; text-align: left;">

Go to "API Extensions"

</foreignObject><text x="111" y="224" fill="rgb(0, 0, 0)" font-family="Helvetica" font-size="12px" text-anchor="middle">Go to "API Extensions"</text></switch></g><rect x="252.79" y="31.94" width="100.63" height="41.13" fill="none" stroke="none" pointer-events="all"/><g transform="translate(-0.5 -0.5)scale(0.7)"><switch><foreignObject pointer-events="none" width="143%" height="143%" requiredFeatures="http://www.w3.org/TR/SVG11/feature#Extensibility" style="overflow: visible; text-align: left;">

Do you want to add entirely new types to the Kubernetes API?

</foreignObject><text x="363" y="80" fill="#FFFFFF" font-family="Helvetica" font-size="16px">Do you want to add...</text></switch></g><ellipse cx="630.35" cy="52.51" rx="47.25" ry="31.499999999999996" fill="#454545" stroke="none" pointer-events="all"/><g transform="translate(-0.5 -0.5)scale(0.7)"><switch><foreignObject pointer-events="none" width="143%" height="143%" requiredFeatures="http://www.w3.org/TR/SVG11/feature#Extensibility" style="overflow: visible; text-align: left;">

NO

</foreignObject><text x="901" y="79" fill="rgb(0, 0, 0)" font-family="Helvetica" font-size="12px" text-anchor="middle">NO</text></switch></g><rect x="564.07" y="189" width="152.03" height="35" fill="none" stroke="none" pointer-events="all"/><g transform="translate(-0.5 -0.5)scale(0.7)"><switch><foreignObject pointer-events="none" width="143%" height="143%" requiredFeatures="http://www.w3.org/TR/SVG11/feature#Extensibility" style="overflow: visible; text-align: left;">

Do you want to restrict or automatically edit fields in some or all API types?

</foreignObject><text x="808" y="300" fill="rgb(0, 0, 0)" font-family="Helvetica" font-size="16px">Do you want to restrict or...</text></switch></g><ellipse cx="448.35" cy="206.5" rx="47.25" ry="31.499999999999996" fill="#454545" stroke="none" pointer-events="all"/><g transform="translate(-0.5 -0.5)scale(0.7)"><switch><foreignObject pointer-events="none" width="143%" height="143%" requiredFeatures="http://www.w3.org/TR/SVG11/feature#Extensibility" style="overflow: visible; text-align: left;">

YES

</foreignObject><text x="641" y="299" fill="rgb(0, 0, 0)" font-family="Helvetica" font-size="12px" text-anchor="middle">YES</text></switch></g><path d="M 495.6 206.5 L 513.1 206.5" fill="none" stroke="rgb(0, 0, 0)" stroke-width="0.7" stroke-miterlimit="10" pointer-events="stroke"/><rect x="371.35" y="280" width="154" height="42" fill="#ffffff" stroke="#000000" stroke-width="1.05" pointer-events="all"/><g transform="translate(-0.5 -0.5)scale(0.7)"><switch><foreignObject pointer-events="none" width="143%" height="143%" requiredFeatures="http://www.w3.org/TR/SVG11/feature#Extensibility" style="overflow: visible; text-align: left;">

Go to "API Access Extensions"

</foreignObject><text x="641" y="434" fill="rgb(0, 0, 0)" font-family="Helvetica" font-size="12px" text-anchor="middle">Go to "API Access Extensions"</text></switch></g><ellipse cx="630.35" cy="311.5" rx="47.25" ry="31.499999999999996" fill="#454545" stroke="none" pointer-events="all"/><g transform="translate(-0.5 -0.5)scale(0.7)"><switch><foreignObject pointer-events="none" width="143%" height="143%" requiredFeatures="http://www.w3.org/TR/SVG11/feature#Extensibility" style="overflow: visible; text-align: left;">

NO

</foreignObject><text x="901" y="449" fill="rgb(0, 0, 0)" font-family="Helvetica" font-size="12px" text-anchor="middle">NO</text></switch></g><path d="M 630.35 364 L 749.35 416.5 L 630.35 469 L 511.35 416.5 Z" fill="#326ce6" stroke="none" pointer-events="all"/><rect x="555.1" y="399" width="169.75" height="35" fill="none" stroke="none" pointer-events="all"/><g transform="translate(-0.5 -0.5)scale(0.7)"><switch><foreignObject pointer-events="none" width="143%" height="143%" requiredFeatures="http://www.w3.org/TR/SVG11/feature#Extensibility" style="overflow: visible; text-align: left;">

Do you want to change the underlying implementation of the built-in API types?

</foreignObject><text x="795" y="600" fill="rgb(0, 0, 0)" font-family="Helvetica" font-size="16px">Do you want to change the unde...</text></switch></g><ellipse cx="420.35" cy="416.5" rx="47.25" ry="31.499999999999996" fill="#454545" stroke="none" pointer-events="all"/><g transform="translate(-0.5 -0.5)scale(0.7)"><switch><foreignObject pointer-events="none" width="143%" height="143%" requiredFeatures="http://www.w3.org/TR/SVG11/feature#Extensibility" style="overflow: visible; text-align: left;">

YES

</foreignObject><text x="601" y="599" fill="rgb(0, 0, 0)" font-family="Helvetica" font-size="12px" text-anchor="middle">YES</text></switch></g><ellipse cx="586.6" cy="528.5" rx="47.25" ry="31.499999999999996" fill="#454545" stroke="none" pointer-events="all"/><g transform="translate(-0.5 -0.5)scale(0.7)"><switch><foreignObject pointer-events="none" width="143%" height="143%" requiredFeatures="http://www.w3.org/TR/SVG11/feature#Extensibility" style="overflow: visible; text-align: left;">

NO

</foreignObject><text x="838" y="759" fill="rgb(0, 0, 0)" font-family="Helvetica" font-size="12px" text-anchor="middle">NO</text></switch></g><path d="M 420.35 476 L 539.35 528.5 L 420.35 581 L 301.35 528.5 Z" fill="#326ce6" stroke="none" pointer-events="all"/><ellipse cx="742.35" cy="528.5" rx="47.25" ry="31.499999999999996" fill="#454545" stroke="none" pointer-events="all"/><g transform="translate(-0.5 -0.5)scale(0.7)"><switch><foreignObject pointer-events="none" width="143%" height="143%" requiredFeatures="http://www.w3.org/TR/SVG11/feature#Extensibility" style="overflow: visible; text-align: left;">

NO

</foreignObject><text x="1061" y="759" fill="rgb(0, 0, 0)" font-family="Helvetica" font-size="12px" text-anchor="middle">NO</text></switch></g><ellipse cx="254.1" cy="528.5" rx="47.25" ry="31.499999999999996" fill="#454545" stroke="none" pointer-events="all"/><g transform="translate(-0.5 -0.5)scale(0.7)"><switch><foreignObject pointer-events="none" width="143%" height="143%" requiredFeatures="http://www.w3.org/TR/SVG11/feature#Extensibility" style="overflow: visible; text-align: left;">

YES

</foreignObject><text x="363" y="759" fill="rgb(0, 0, 0)" font-family="Helvetica" font-size="12px" text-anchor="middle">YES</text></switch></g><rect x="356.47" y="504" width="177.63" height="49" fill="none" stroke="none" pointer-events="all"/><g transform="translate(-0.5 -0.5)scale(0.7)"><switch><foreignObject pointer-events="none" width="143%" height="143%" requiredFeatures="http://www.w3.org/TR/SVG11/feature#Extensibility" style="overflow: visible; text-align: left;">

Do you want ot change Volumes, Services, Ingresses, PersistentVolumes?

</foreignObject><text x="511" y="760" fill="rgb(0, 0, 0)" font-family="Helvetica" font-size="16px">Do you want ot change Volumes, S...</text></switch></g><rect x="177.1" y="595" width="154" height="42" fill="#ffffff" stroke="#000000" stroke-width="1.05" pointer-events="all"/><g transform="translate(-0.5 -0.5)scale(0.7)"><switch><foreignObject pointer-events="none" width="143%" height="143%" requiredFeatures="http://www.w3.org/TR/SVG11/feature#Extensibility" style="overflow: visible; text-align: left;">

Go to "Infrastructure"

</foreignObject><text x="363" y="884" fill="rgb(0, 0, 0)" font-family="Helvetica" font-size="12px" text-anchor="middle">Go to "Infrastructure"</text></switch></g><rect x="509.6" y="595" width="154" height="42" fill="#ffffff" stroke="#000000" stroke-width="1.05" pointer-events="all"/><g transform="translate(-0.5 -0.5)scale(0.7)"><switch><foreignObject pointer-events="none" width="143%" height="143%" requiredFeatures="http://www.w3.org/TR/SVG11/feature#Extensibility" style="overflow: visible; text-align: left;">

Go to "Automation"

</foreignObject><text x="838" y="884" fill="rgb(0, 0, 0)" font-family="Helvetica" font-size="12px" text-anchor="middle">Go to "Automation"</text></switch></g><path d="M 124.6 52.5 L 189.1 53.23" fill="none" stroke="#000000" stroke-width="0.7" stroke-miterlimit="10" pointer-events="stroke"/><path d="M 77.35 133 L 77.35 84" fill="none" stroke="#000000" stroke-width="0.7" stroke-miterlimit="10" pointer-events="stroke"/><path d="M 583.1 52.51 L 420.2 52.5" fill="none" stroke="#000000" stroke-width="0.7" stroke-miterlimit="10" pointer-events="stroke"/><path d="M 630.35 154 L 630.35 84.01" fill="none" stroke="#000000" stroke-width="0.7" stroke-miterlimit="10" pointer-events="stroke"/><path d="M 630.35 280 L 630.35 259" fill="none" stroke="rgb(0, 0, 0)" stroke-width="0.7" stroke-miterlimit="10" pointer-events="stroke"/><path d="M 630.35 364 L 630.35 343" fill="none" stroke="rgb(0, 0, 0)" stroke-width="0.7" stroke-miterlimit="10" pointer-events="stroke"/><path d="M 448.35 280 L 448.35 238" fill="none" stroke="rgb(0, 0, 0)" stroke-width="0.7" stroke-miterlimit="10" pointer-events="stroke"/><path d="M 467.6 416.5 L 514.44 416.39" fill="none" stroke="rgb(0, 0, 0)" stroke-width="0.7" stroke-miterlimit="10" pointer-events="stroke"/><path d="M 420.35 476.63 L 420.35 448" fill="none" stroke="rgb(0, 0, 0)" stroke-width="0.7" stroke-miterlimit="10" pointer-events="stroke"/><path d="M 254.1 595 L 254.1 560" fill="none" stroke="rgb(0, 0, 0)" stroke-width="0.7" stroke-miterlimit="10" pointer-events="stroke"/><path d="M 586.6 595 L 586.6 560" fill="none" stroke="rgb(0, 0, 0)" stroke-width="0.7" stroke-miterlimit="10" pointer-events="stroke"/><path d="M 789.6 528.5 L 807.1 528.5 L 807.1 416.5 L 747.21 416.5" fill="none" stroke="rgb(0, 0, 0)" stroke-width="0.7" stroke-miterlimit="10" pointer-events="stroke"/><path d="M 663.6 616 L 681.1 616 L 681.1 528.5 L 695.1 528.5" fill="none" stroke="rgb(0, 0, 0)" stroke-width="0.7" stroke-miterlimit="10" pointer-events="stroke"/></g><switch><g requiredFeatures="http://www.w3.org/TR/SVG11/feature#Extensibility"/><text text-anchor="middle" font-size="10px" x="50%" y="100%">Text is not SVG - cannot display</text></switch></svg>   No newline at end of file

In the "Extension point choice flowchart", answering yes to the first questions leads to: Go the "Adding APIs" Section" There's a grammar error and a punctuation error, but major problem is that there is no such section on that page. It should read: Go to "API extensions"
Page related issue /language en /sig docs
This issue is talking about the first section of this diagram at given page ! /kind feature
Thank you for your reply but basically this approach is not the good practice The issue has been defined by the and the link to redirect to that page is not been provided so it has been provided by and you are giving the screenshot of that issue means it does not looks good. Requesting you for the good approach. Its asking like the issue is denoted by the description and then by link and then by image.
When i saw this issue, it was having relevant explanation, and link of the page by niranjan but i felt an image is missing to understand the issue better like - where this "Go the adding API server is written" in whole page and where we need to make change. So, i just one image. Generally, i don't put pic of an issue like this. When i approach an issue i first try to understand it, then verify it then label it and then try to discuss about its causes and possible solutions in proper way that won't look odd to anyone. But here forgive me if this looked odd to you, thank you for your feedback. Now i will take care even more.
/priority backlog /triage accepted For more tips about diagram improvements, see
/retitle Wrong wording in diagram at
Hi! I think I'll be able to solve this one. Also, I think this diagram's made using instead of I should remake it using the same tool, right? /assign
Using is fine It'd be nice to also use Kubernetes colors - maybe a second PR?
That sounds good! Sure, I can create a second PR after this one. And just to clarify, should I open a new issue for it, or can I proceed directly with the pull request? I'm a new contributor to the Kubernetes project :)
You can proceed directly with a PR, no need to raise a new issue for it.


Question: <ins> --- title: WindowsデバッグTips content_type: concept --- <!-- overview --> <!-- body --> ## ノードレベルのトラブルシューティング{#troubleshooting-node} 1. Podが"Container Creating"と表示されたまま動かなくなったり、何度も再起動を繰り返します pauseイメージがWindows OSのバージョンと互換性があることを確認してください。 最新/推奨のpauseイメージや詳細情報については、[Pauseコンテナ](/docs/concepts/windows/intro/#pause-container)を参照してください。 {{< note >}} コンテナランタイムとしてcontainerdを使用している場合、pauseイメージはconfig.toml設定ファイルの`plugins.plugins.cri.sandbox_image`フィールドで指定されます。 {{< /note >}} 1. Podが`ErrImgPull`または`ImagePullBackOff`のステータスを表示します Podが[互換性](https://learn.microsoft.com/ja-jp/virtualization/windowscontainers/deploy-containers/version-compatibility)のあるWindowsノードにスケジュールされていることを確認してください。 Podに対して互換性のあるノードを指定する方法の詳細については、[このガイド](/docs/concepts/windows/user-guide/#ensuring-os-specific-workloads-land-on-the-appropriate-container-host)を参照してください。 ## ネットワークのトラブルシューティング{#troubleshooting-network} 1. Windows Podがネットワークに接続できません 仮想マシンを使用している場合は、すべてのVMのネットワークアダプターでMACスプーフィングが**有効**になっていることを確認してください。 1. Windows Podから外部リソースにpingできません Windows Podには、ICMPプロトコル用にプログラムされたアウトバウンドルールはありません。ただし、TCP/UDPはサポートされています。 クラスター外のリソースへの接続を実証する場合は、`ping <IP>`を対応する`curl <IP>`コマンドに置き換えてください。 それでも問題が解決しない場合は、[cni.conf](https://github.com/Microsoft/SDN/blob/master/Kubernetes/flannel/l2bridge/cni/config/cni.conf)のネットワーク設定に問題がある可能性が高いです。 この静的ファイルはいつでも編集できます。 設定の更新は、新しく作成されたすべてのKubernetesリソースに適用されます。 Kubernetesのネットワーク要件の1つ([Kubernetesモデル](/ja/docs/concepts/cluster-administration/networking/)を参照)は、内部でNATせずにクラスター通信が行われることです。 この要件を満たすために、アウトバウンドのNATを発生させたくないすべての通信のための[ExceptionList](https://github.com/Microsoft/SDN/blob/master/Kubernetes/flannel/l2bridge/cni/config/cni.conf#L20)があります。 ただしこれは、クエリしようとしている外部IPを`ExceptionList`から除外する必要があることも意味します。 そうして初めて、Windows Podからのトラフィックが正しくSNATされ、外部からの応答を受信できるようになります。 この点について、`cni.conf`の`ExceptionList`は次のようになります: ```conf "ExceptionList": [ "10.244.0.0/16",  # クラスターのサブネット "10.96.0.0/12",   # Serviceのサブネット "10.127.130.0/24" # 管理(ホスト)のサブネット ] ``` 1. Windowsノードが`NodePort`タイプのServiceにアクセスできません ノード自身からのローカルNodePortへのアクセスは失敗します。 これは既知の制限です。 NodePortへのアクセスは、他のノードや外部のクライアントからは動作します。 1. コンテナのvNICとHNSエンドポイントが削除されています この問題は`hostname-override`パラメーターが[kube-proxy](/docs/reference/command-line-tools-reference/kube-proxy/) に渡されていない場合に発生する可能性があります。 これを解決するためには、ユーザーは次のようにkube-proxyにホスト名を渡す必要があります: ```powershell C:kkube-proxy.exe --hostname-override=$(hostname) ``` 1. WindowsノードがService IPを使用してサービスにアクセスできません これはWindows上のネットワークスタックの既知の制限です。 ただし、Windows PodはService IPにアクセスできます。 1. kubeletの起動時にネットワークアダプターが見つかりません Windowsのネットワーキングスタックでは、Kubernetesネットワーキングが動作するために仮想アダプターが必要です。 (管理者シェルで)次のコマンドを実行しても結果が返されない場合、kubeletが動作するために必要な前提条件である仮想ネットワークの作成に失敗しています。 ```powershell Get-HnsNetwork | ? Name -ieq "cbr0" Get-NetAdapter | ? Name -Like "vEthernet (Ethernet*" ``` ホストのネットワークアダプターが"Ethernet"ではない場合、`start.ps1`スクリプトの[InterfaceName](https://github.com/microsoft/SDN/blob/master/Kubernetes/flannel/start.ps1#L7)パラメーターを修正することが有益です。 それ以外の場合は、`start-kubelet.ps1`スクリプトの出力結果を参照して、仮想ネットワークの作成中にエラーが発生していないか確認します。 1. DNS名前解決が正しく動作しません この[セクション](/ja/docs/concepts/services-networking/dns-pod-service/#dns-windows)のWindowsにおけるDNSの制限について確認してください。 1. `kubectl port-forward`が"unable to do port forwarding: wincat not found"で失敗します これは、pauseインフラコンテナ`mcr.microsoft.com/oss/kubernetes/pause:3.6`に`wincat.exe`を含める形で、Kubernetes 1.15にて実装されました。 必ずサポートされたKubernetesのバージョンを使用してください。 独自のpauseインフラコンテナをビルドしたい場合は、必ず[wincat](https://github.com/kubernetes/kubernetes/tree/master/build/pause/windows/wincat)を含めるようにしてください。 1. Windows Serverノードがプロキシの背後にあるため、Kubernetesのインストールに失敗しています プロキシの背後にある場合は、次のPowerShell環境変数が定義されている必要があります: ```PowerShell [Environment]::SetEnvironmentVariable("HTTP_PROXY", "http://proxy.example.com:80/", [EnvironmentVariableTarget]::Machine) [Environment]::SetEnvironmentVariable("HTTPS_PROXY", "http://proxy.example.com:443/", [EnvironmentVariableTarget]::Machine) ``` ### Flannelのトラブルシューティング 1. Flannelを使用すると、クラスターに再参加した後にノードに問題が発生します 以前に削除したノードがクラスターに再参加すると、flanneldはノードに新しいPodサブネットを割り当てようとします。 ユーザーは、次のパスにある古いPodサブネットの設定ファイルを削除する必要があります: ```powershell Remove-Item C:kSourceVip.json Remove-Item C:kSourceVipRequest.json ``` 1. Flanneldが"Waiting for the Network to be created"と表示されたままになります この[Issue](https://github.com/coreos/flannel/issues/1066)に関する多数の報告があります; 最も可能性が高いのは、flannelネットワークの管理IPが設定されるタイミングの問題です。 回避策は、`start.ps1`を再度実行するか、次のように手動で再起動することです: ```powershell [Environment]::SetEnvironmentVariable("NODE_NAME", "<Windows_Worker_Hostname>") C:flannelflanneld.exe --kubeconfig-file=c:kconfig --iface=<Windows_Worker_Node_IP> --ip-masq=1 --kube-subnet-mgr=1 ``` 1. `/run/flannel/subnet.env`が見つからないためにWindows Podが起動しません これはFlannelが正常に起動できなかったことを示しています。 `flanneld.exe`を再起動するか、Kubernetesマスター上の`/run/flannel/subnet.env`をWindowsワーカーノード上の`C:runflannelsubnet.env`に手動でコピーして、`FLANNEL_SUBNET`行を異なる数値に変更します。 例えば、ノードのサブネットを10.244.4.1/24としたい場合は次のようにします: ```env FLANNEL_NETWORK=10.244.0.0/16 FLANNEL_SUBNET=10.244.4.1/24 FLANNEL_MTU=1500 FLANNEL_IPMASQ=true ``` ### さらなる調査 これらの手順で問題が解決しない場合は、下記からKubernetesのWindowsノード上でWindowsコンテナを実行するためのヘルプを得ることができます: * StackOverflowの[Windows Server Container](https://stackoverflow.com/questions/tagged/windows-server-container)トピック * Kubernetesの公式フォーラム[discuss.kubernetes.io](https://discuss.kubernetes.io/) * Kubernetes Slack [#SIG-Windowsチャンネル](https://kubernetes.slack.com/messages/sig-windows) </ins>

This is a Feature Request What would you like to be Translate Japanese Why is this needed There is no Japanese translation for this page Comments File to translate: Original: ref. Japanese Localization document: /area localization /language ja /help
This request has been marked as needing help from a contributor. Please ensure that the issue body includes answers to the following questions: Why are we solving this issue? To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points? Does this issue have zero to low barrier of entry? How can the assignee reach out to you for help? For more details on the requirements of such an issue, please see and ensure that they are met. If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : This is a Feature Request Original: /language ja /help </details
/retitle [ja] Translate into Japanese
/triage accepted
/assign


Question:
 --- layout: blog title: "比较本地 Kubernetes 开发工具：Telepresence、Gefyra 和 mirrord" date: 2023-09-12 slug: local-k8s-development-tools ---   **作者:** Eyal Bukchin (MetalBear) **译者:** [Michael Yao](https://github.com/windsonsea) (DaoCloud)  Kubernetes 的开发周期是一个不断演化的领域，有许多工具在寻求简化这个过程。 每个工具都有其独特的方法，具体选择通常取决于各个项目的要求、团队的专业知识以及所偏好的工作流。  在各种解决方案中，我们称之为“本地 K8S 开发工具”的一个类别已渐露端倪， 这一类方案通过将本地运行的组件连接到 Kubernetes 集群来提升 Kubernetes 开发体验。 这样可以在云环境中快速测试新代码，避开了 Docker 化、CI 和部署这样的传统周期。 在本文中，我们将比较这个类别中的三个解决方案：Telepresence、Gefyra 和我们自己的挑战者 mirrord。 ## Telepresence  [Telepresence](https://www.telepresence.io/) 是这类工具中最早也最成熟的解决方案， 它使用 VPN（或更具体地说，一个 `tun` 设备）将用户的机器（或本地运行的容器）与集群的网络相连。 它支持拦截发送到集群中特定服务的传入流量，并将其重定向到本地端口。 被重定向的流量还可以被过滤，以避免完全破坏远程服务。 它还提供了一些补充特性，如支持文件访问（通过本地挂载卷将其挂载到 Pod 上）和导入环境变量。 Telepresence 需要在用户的机器上安装一个本地守护进程（需要 root 权限），并在集群上运行一个 Traffic Manager 组件。此外，它在 Pod 上以边车的形式运行一个 Agent 来拦截所需的流量。 ## Gefyra  [Gefyra](https://gefyra.dev/) 与 Telepresence 类似，也采用 VPN 连接到集群。 但 Gefyra 只支持将本地运行的 Docker 容器连接到集群。 这种方法增强了在不同操作系统和本地设置环境之间的可移植性。 然而，它的缺点是不支持原生运行非容器化的代码。  Gefyra 主要关注网络流量，不支持文件访问和环境变量。 与 Telepresence 不同，Gefyra 不会改变集群中的工作负载， 因此如果发生意外情况，清理过程更加简单明了。 ## mirrord  作为这三个工具中最新的工具，[mirrord](https://mirrord.dev/)采用了一种不同的方法， 它通过将自身注入到本地二进制文件中（在 Linux 上利用 `LD_PRELOAD`，在 macOS 上利用 `DYLD_INSERT_LIBRARIES`）， 并重写 libc 函数调用，然后代理到在集群中运行的临时代理。 例如，当本地进程尝试读取一个文件时，mirrord 会拦截该调用并将其发送到该代理， 该代理再从远程 Pod 读取文件。这种方法允许 mirrord 覆盖进程的所有输入和输出，统一处理网络访问、文件访问和环境变量。  通过在进程级别工作，mirrord 支持同时运行多个本地进程，每个进程都在集群中的相应 Pod 上下文中运行， 无需将这些进程容器化，也无需在用户机器上获取 root 权限。  ## 摘要   {#summary}

比较 Telepresence、Gefyra 和 mirrord

 	 Telepresence	 Gefyra	 mirrord

  集群连接作用域	 整台机器或容器	 容器	 进程

  开发者操作系统支持	 Linux、macOS、Windows	 Linux、macOS、Windows	 Linux、macOS、Windows (WSL)

  传入的流量特性	 拦截	 拦截	 拦截或镜像

  文件访问	 已支持	 不支持	 已支持

  环境变量	 已支持	 不支持	 已支持

  需要本地 root	 是	 否	 否

  如何使用

CLI

Docker Desktop 扩展

CLI

Docker Desktop 扩展

CLI

Visual Studio Code 扩展

IntelliJ 插件

  ## 结论   {#conclusion} Telepresence、Gefyra 和 mirrord 各自提供了独特的方法来简化 Kubernetes 开发周期， 每个工具都有其优缺点。Telepresence 功能丰富但复杂，mirrord 提供无缝体验并支持各种功能， 而 Gefyra 则追求简单和稳健。  你的选择应取决于项目的具体要求、团队对工具的熟悉程度以及所需的开发工作流。 无论你选择哪个工具，我们相信本地 Kubernetes 开发方法都可以提供一种简单、有效和低成本的解决方案， 来应对 Kubernetes 开发周期中的瓶颈，并且随着这些工具的不断创新和发展，这种本地方法将变得更加普遍。

I will localize the blog: To avoid any conflict that may occur, this issue is opened. /assign /language zh
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


Question: {{< feature-state for_k8s_version="v1.21" state="stable" >}} <del> You can configure the kubelet to rotate logs automatically. If you configure rotation, the kubelet is responsible for rotating container logs and managing the </del> <ins> The kubelet is responsible for rotating container logs and managing the </ins> logging directory structure. The kubelet sends this information to the container runtime (using CRI), and the runtime writes the container logs to the given location. You can configure two kubelet [configuration settings](/docs/reference/config-api/kubelet-config.v1beta1/), <del> `containerLogMaxSize` and `containerLogMaxFiles`, </del> <ins> `containerLogMaxSize` (default 10Mi) and `containerLogMaxFiles` (default 5), </ins> using the [kubelet configuration file](/docs/tasks/administer-cluster/kubelet-config-file/). These settings let you configure the maximum size for each log file and the maximum number of files allowed for each container respectively.

On Since the "Log rotation" feature is stable and , we may remove the words "You can configure" and "If you configure rotation". BTW, it would be good to mention the following default values, refer to
/language en /sig docs
/sig node
/assign
/kind bug Any updates?
/remove-kind bug /kind feature
/remove-kind feature /kind docs
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /remove-kind feature /kind docs 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 think mentioning the defaults for kubelet configuration would be useful. /triage accepted
/priority backlog
/assign


Question: ## Determine which version to upgrade to <del> 1.  Find the latest stable 1.18 version: </del> <ins> Find the latest stable 1.18 version: </ins> <del> {{< tabs name="k8s_install_versions" >}} {{% tab name="Ubuntu, Debian or HypriotOS" %}} </del> <ins> {{< tabs name="k8s_install_versions" >}} {{% tab name="Ubuntu, Debian or HypriotOS" %}} </ins> apt update apt-cache madison kubeadm # find the latest 1.18 version in the list # it should look like 1.18.x-00, where x is the latest patch <del> {{% /tab %}} {{% tab name="CentOS, RHEL or Fedora" %}} </del> <ins> {{% /tab %}} {{% tab name="CentOS, RHEL or Fedora" %}} </ins> yum list --showduplicates kubeadm --disableexcludes=kubernetes # find the latest 1.18 version in the list # it should look like 1.18.x-0, where x is the latest patch <del> {{% /tab %}} {{< /tabs >}} </del> <ins> {{% /tab %}} {{< /tabs >}} </ins> ## Upgrading control plane nodes ### Upgrade the first control plane node <del> 1.  On your first control plane node, upgrade kubeadm: </del> <ins> -  On your first control plane node, upgrade kubeadm: </ins> <del> {{< tabs name="k8s_install_kubeadm_first_cp" >}} {{% tab name="Ubuntu, Debian or HypriotOS" %}} </del> <ins> {{< tabs name="k8s_install_kubeadm_first_cp" >}} {{% tab name="Ubuntu, Debian or HypriotOS" %}} </ins> # replace x in 1.18.x-00 with the latest patch version apt-mark unhold kubeadm &&  apt-get update && apt-get install -y kubeadm=1.18.x-00 &&  apt-mark hold kubeadm <ins> - </ins> # since apt-get version 1.1 you can also use the following method apt-get update &&  apt-get install -y --allow-change-held-packages kubeadm=1.18.x-00 <del> {{% /tab %}} {{% tab name="CentOS, RHEL or Fedora" %}} </del> <ins> {{% /tab %}} {{% tab name="CentOS, RHEL or Fedora" %}} </ins> # replace x in 1.18.x-0 with the latest patch version yum install -y kubeadm-1.18.x-0 --disableexcludes=kubernetes <del> {{% /tab %}} {{< /tabs >}} </del> <ins> {{% /tab %}} {{< /tabs >}} </ins> <del> 1.  Verify that the download works and has the expected version: </del> <ins> -  Verify that the download works and has the expected version: </ins> ```shell kubeadm version ``` <del> 1.  Drain the control plane node: </del> <ins> -  Drain the control plane node: </ins> ```shell # replace <cp-node-name> with the name of your control plane node kubectl drain <cp-node-name> --ignore-daemonsets ``` <del> 1.  On the control plane node, run: </del> <ins> -   On the control plane node, run: </ins> ```shell sudo kubeadm upgrade plan

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--indentation issue Proposed Solution: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--18 <!--Additional Information:--fix the page indentation
/sig cluster-lifecycle docs hi, can you show which section you think is wrong or maybe provide a screenshot?
/sig cluster-lifecycle docs Attached screenshots
i don't see the attachments, possibly because you replied via email. try adding them using the GitHub web UI.
! ! ! !
Page alignment or indentation not proper looks.
ok, i can confirm this. hi, was this broken by this PR, or maybe something on the hugo side changed recently?
The Hugo upgrade was PR
/kind bug /priority important-longterm
I've tried to make a work around for this. It looks like tabs shortcodes with code snippets inside them don't play well with shortcodes (see issue ).
I will take a stab at cleaning this up assuming work isn't currently being done. We might have to adjust the page slightly until capture is removed. /assign
I can share some WIP in case it helps
thanks for taking a look and
oof, sorry I saw this after I opened the PR. That does help! I was scratching my head on some of these bugs. Let me know if you want me to modify my PR to incorporate some of your suggestions or vice versa. I was poking fun of the page on twitter and felt obligated to try to fix it :smile:
Busy at the moment I'm afraid. Feel free to snarf any bits that look useful.


Question: {{< glossary_tooltip term_id="kubeadm" text="kubeadm" >}} 도구를 사용하여 쿠버네티스 클러스터를 만들고 관리할 수 있다. 사용자 친화적인 방식으로 최소한의 실행 가능하고 안전한 클러스터를 설정하고 실행하는 데 필요한 작업을 수행한다.  [kubeadm 설치](/docs/setup/production-environment/tools/kubeadm/install-kubeadm/) 페이지는 kubeadm 설치하는 방법을 보여준다.   [kubeadm 설치](/ko/docs/setup/production-environment/tools/kubeadm/install-kubeadm/) 페이지는 kubeadm 설치하는 방법을 보여준다.  설치가 끝나면, [클러스터 생성](/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm/)이 가능하다.  kubeadm 설치 가이드 보기   kubeadm 설치 가이드 보기

<!-- 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: In , the link href is (English). The of is recently in . Proposed Solution: In , Before: After: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/assign
/language ko
/triage accepted
Resolved by


Question: * Пробуете или начинаете работу с Kubernetes * Локально разрабатываете и тестируете кластер <del> Выбрать [решение для запуска на локальной машине](/docs/setup/pick-right-solution/#local-machine-solutions). </del> <ins> Выбрать [решение для запуска на локальной машине](/docs/setup/learning-environment/). </ins> ## Управляемые решения

По ссылке получаю страницу "404"
/language ru /kind bug
Страница на текущий момент не вся актуальна. Используйте английскую версию.
/triage accepted


Question:
  --cloud-provider-gce-l7lb-src-cidrs cidrs     Default: 130.211.0.0/22,35.191.0.0/16

CIDRs opened in GCE firewall for L7 LB traffic proxy & health checks

 --cloud-provider-gce-lb-src-cidrs cidrs     Default: 130.211.0.0/22,209.85.152.0/22,209.85.204.0/22,35.191.0.0/16

CIDRs opened in GCE firewall for L4 LB traffic proxy & health checks

  --cluster-cidr string

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: ! xref: Has references to some CLI arguments that are not valid for . Seem to be side effect of changes went into Proposed Solution: Remove the invalid flags from the documentation in Page to Update:
/language en /triage accepted
/assign
/assign
Thanks for taking care of this :)


Question:
Type: Counter

Labels:type

apiserver_nodeport_repair_reconcile_errors_total

Number of reconciliation failures on the nodeport repair reconcile loop

Stability Level:ALPHA

Type: Counter

apiserver_request_aborts_total

Number of requests which apiserver aborted possibly due to a timeout, for each group, version, verb, resource, subresource and scope

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: removed metric from the documented metrics for Kubernetes v1.30, but the metric is still collected for the API server (ref: and ). Proposed Solution: Reinstate the documentation for such metric. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--Kubernetes Version: v1.30 <!--Additional Information:--
/sig instrumentation
/triage accepted
This metrics exists in the file generated by . Or there is a problem with the file generated by before. Let me generate the metrics file again and see. /assign
After I re-ran the script, some metrics were indeed missing (not just metrics ), it was a problem with the generated script, I will take a closer look.


Question: weight: 50 description: > Understand Pods, the smallest deployable compute object in Kubernetes, and the higher-level abstractions that help you to run them. <ins> no_list: true </ins> --- <ins> {{< glossary_definition term_id="workload" length="short" >}} Whether your workload is a single component or several that work together, on Kubernetes you run it inside a set of [Pods](/docs/concepts/workloads/pods). In Kubernetes, a Pod represents a set of running {{< glossary_tooltip text="containers" term_id="container" >}} on your cluster. A Pod has a defined lifecycle. For example, once a Pod is running in your cluster then a critical failure on the {{< glossary_tooltip text="node" term_id="node" >}} where that Pod is running means that all the Pods on that node fail. Kubernetes treats that level of failure as final: you would need to create a new Pod even if the node later recovers. However, to make life considerably easier, you don't need to manage each Pod directly. Instead, you can use _workload resources_ that manage a set of Pods on your behalf. These resources configure {{< glossary_tooltip term_id="controller" text="controllers" >}} that make sure the right number of the right kind of Pod are running, to match the state you specified. Those workload resources include: * [Deployment](/docs/concepts/workloads/controllers/deployment/) and [ReplicaSet](/docs/concepts/workloads/controllers/replicaset/) (replacing the legacy resource {{< glossary_tooltip text="ReplicationController" term_id="replication-controller" >}}); * [StatefulSet](/docs/concepts/workloads/controllers/statefulset/); * [DaemonSet](/docs/concepts/workloads/controllers/daemonset/) for running Pods that provide node-local facilities, such as a storage driver or network plugin; * [Job](/docs/concepts/workloads/controllers/job/) and [CronJob](/docs/concepts/workloads/controllers/cronjob/) for tasks that run to completion. There are also two supporting concepts that you might find relevant: * [Garbage collection](/docs/concepts/workloads/controllers/garbage-collection/) tidies up objects from your cluster after their _owning resource_ has been removed. * The [_time-to-live after finished_ controller](/docs/concepts/workloads/controllers/ttlafterfinished/) removes Jobs once a defined time has passed since they completed. ## {{% heading "whatsnext" %}} As well as reading about each resource, you can learn about specific tasks that relate to them: * [Run a stateless application using a Deployment](/docs/tasks/run-application/run-stateless-application-deployment/) * Run a stateful application either as a [single instance](/docs/tasks/run-application/run-single-instance-stateful-application/) or as a [replicated set](/docs/tasks/run-application/run-replicated-stateful-application/) * [Run Automated Tasks with a CronJob](/docs/tasks/job/automated-tasks-with-cron-jobs/) Once your application is running, you might want to make it available on the internet as a [Service](/docs/concepts/services-networking/service/) or, for web application only, using an [Ingress](/docs/concepts/services-networking/ingress). You can also visit [Configuration](/docs/concepts/configuration/) to learn about Kubernetes' mechanisms for separating code from configuration. </ins>

This "Workloads" doc page just has two links to Pods and Controllers. It would be great to give an overview of the purpose of workloads (why such an architectural construct is required? and how it is used in Kubernetes). Thanks.
An introduction to the workload concepts would be really useful /kind feature /language en /priority backlog
/triage accepted


Question: One of the nodes is now running the counter pod: <del> ![Counter Pod](https://raw.githubusercontent.com/kubernetes/kubernetes/{{page.githubbranch}}/examples/blog-logging/diagrams/27gf-counter.png) </del> <ins> ![image](/images/blog-logging/diagrams/27gf-counter.png) </ins> When the pod status changes to `Running` we can use the kubectl logs command to view the output of this counter pod.

Here "Cluster" is a broken link: Perhaps this is an issue with : there is no in master branch, but there in branch. Same issue with below on the same page.


Question:
 // The page and script is loaded successfully $(document).ready(function() { // Function to handle hover over
 elements function handleFigureHover() { // Only change cursor to zoom-in if figure has 'clickable-zoom' class if ($(this).hasClass('clickable-zoom') && !$(this).hasClass('figure-fullscreen-content')) { $(this).css('cursor', 'zoom-in'); } } // Attach hover event to
 elements with 'clickable-zoom' class $('figure.clickable-zoom').hover(handleFigureHover, function() { // Mouse out - revert cursor back to default $(this).css('cursor', 'default'); }); // Attach click event to
 elements with 'clickable-zoom' class $('figure.clickable-zoom').click(function() { var $figure = $(this); // Check if the figure has 'clickable-zoom' class if ($figure.hasClass('clickable-zoom')) { var $img = $figure.find('img'); // Get the  element within the clicked
 // Toggle 'figure-zoomed' class to scale the image $img.toggleClass('figure-zoomed'); // Create a full-screen overlay var $fullscreenOverlay = $('

'); // Clone the  element to display in full-screen var $fullscreenImg = $img.clone(); $fullscreenImg.addClass('figure-fullscreen-img'); // Append the full-screen image to the overlay $fullscreenOverlay.append($fullscreenImg); // Create a close button for the full-screen overlay var $closeButton = $('×'); $closeButton.click(function() { // Remove the full-screen overlay when close button is clicked $fullscreenOverlay.remove(); $('body').css('overflow', 'auto'); // Restore scrolling to the underlying page // Remove 'figure-zoomed' class to reset image scale $img.removeClass('figure-zoomed'); }); $fullscreenOverlay.append($closeButton); // Append the overlay to the body $('body').append($fullscreenOverlay); // Disable scrolling on the underlying page $('body').css('overflow', 'hidden'); // Close full-screen figure when clicking outside of it (on the overlay) $fullscreenOverlay.click(function(event) { if (event.target === this) { // Clicked on the overlay area (outside the full-screen image) $fullscreenOverlay.remove(); $('body').css('overflow', 'auto'); // Restore scrolling to the underlying page // Remove 'figure-zoomed' class to reset image scale $img.removeClass('figure-zoomed'); } }); } }); });

This is a Feature Request Some images in concepts sections are quite detailed but in normal scope the texts inside of them look small and unreadable. Can we add feature for the images to pop up on clicking? It will add to the user experience as well as ease the pain of zooming out the page in whole. What would you like to be Feature to Pop up images on click Why is this needed The texts and details seem too small to read. Comments Reference of some of the pages where the issue arises: Example to the pop-up view for image:
/area web-development /kind feature
/area web-development Something similar to https://medium- ?
/retitle Enable click-to-zoom for some diagrams and other images
/triage accepted /priority backlog /lifecycle frozen
Thanks , I investigated on hugo's documents regarding any shortcode or feature that provide this functionality. but till now haven't found any.
For now I'll investigate more and try to find out what can work so assigning it to myself /assign
A couple of hints:
There is one more way like the above reference link mentioned, If we put full-resolution images in other paths and do this : It is in case we want minimal change in the code. I'm going to add ways here as I find so the community can vote or suggest which will be better for a clean code
one is a good reference for same functionality with example. I'll try both and raise a PR after that.
We using vector images.
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
My apologies,Due to bandwidth issue couldn't work on this, It's open for other people to self-assign.
This could be a positive and beneficial addition to the website. Worth doing (re-triaging as accepted). /triage accepted /lifecycle frozen
Let me see if I can assist with this. Edit: I request review and feedback on pull request


Question: app: iis-2019 ``` <del> [RuntimeClass]: https://kubernetes.io/docs/concepts/containers/runtime-class/ </del>  No newline at end of file <ins> [RuntimeClass]: https://kubernetes.io/docs/concepts/containers/runtime-class/ </ins>

This is a Feature Request What would you like to be Translate docs/setup/production-environment/windows/user-guide-windows-containers/ into Japanese Why is this needed This page has not been translated. Comments /language ja /assign


Question: フックハンドラーのログは、Podのイベントには表示されません。 ハンドラーが何らかの理由で失敗した場合は、イベントをブロードキャストします。 `PostStart`の場合、これは`FailedPostStartHook`イベントで、`PreStop`の場合、これは`FailedPreStopHook`イベントです。 <del> これらのイベントは `kubectl describe pod <pod_name>`を実行することで見ることができます。 このコマンドの実行によるイベントの出力例をいくつか示します。 </del> <ins> 失敗の`FailedPreStopHook`イベントを自分自身で生成する場合には、[lifecycle-events.yaml](https://raw.githubusercontent.com/kubernetes/website/main/content/en/examples/pods/lifecycle-events.yaml)ファイルに対してpostStartのコマンドを"badcommand"に変更し、適用してください。 `kubectl describe pod lifecycle-demo`を実行した結果のイベントの出力例を以下に示します。 </ins> ``` Events: <del> FirstSeen  LastSeen  Count  From                                                   SubObjectPath          Type      Reason               Message ---------  --------  -----  ----                                                   -------------          --------  ------               ------- 1m         1m        1      {default-scheduler }                                                          Normal    Scheduled            Successfully assigned test-1730497541-cq1d2 to gke-test-cluster-default-pool-a07e5d30-siqd 1m         1m        1      {kubelet gke-test-cluster-default-pool-a07e5d30-siqd}  spec.containers{main}  Normal    Pulling              pulling image "test:1.0" 1m         1m        1      {kubelet gke-test-cluster-default-pool-a07e5d30-siqd}  spec.containers{main}  Normal    Created              Created container with docker id 5c6a256a2567; Security:[seccomp=unconfined] 1m         1m        1      {kubelet gke-test-cluster-default-pool-a07e5d30-siqd}  spec.containers{main}  Normal    Pulled               Successfully pulled image "test:1.0" 1m         1m        1      {kubelet gke-test-cluster-default-pool-a07e5d30-siqd}  spec.containers{main}  Normal    Started              Started container with docker id 5c6a256a2567 38s        38s       1      {kubelet gke-test-cluster-default-pool-a07e5d30-siqd}  spec.containers{main}  Normal    Killing              Killing container with docker id 5c6a256a2567: PostStart handler: Error executing in Docker Container: 1 37s        37s       1      {kubelet gke-test-cluster-default-pool-a07e5d30-siqd}  spec.containers{main}  Normal    Killing              Killing container with docker id 8df9fdfd7054: PostStart handler: Error executing in Docker Container: 1 38s        37s       2      {kubelet gke-test-cluster-default-pool-a07e5d30-siqd}                         Warning   FailedSync           Error syncing pod, skipping: failed to "StartContainer" for "main" with RunContainerError: "PostStart handler: Error executing in Docker Container: 1" 1m         22s       2      {kubelet gke-test-cluster-default-pool-a07e5d30-siqd}  spec.containers{main}  Warning   FailedPostStartHook </del> <ins> Type     Reason               Age              From               Message ----     ------               ----             ----               ------- Normal   Scheduled            7s               default-scheduler  Successfully assigned default/lifecycle-demo to ip-XXX-XXX-XX-XX.us-east-2... Normal   Pulled               6s               kubelet            Successfully pulled image "nginx" in 229.604315ms Normal   Pulling              4s (x2 over 6s)  kubelet            Pulling image "nginx" Normal   Created              4s (x2 over 5s)  kubelet            Created container lifecycle-demo-container Normal   Started              4s (x2 over 5s)  kubelet            Started container lifecycle-demo-container Warning  FailedPostStartHook  4s (x2 over 5s)  kubelet            Exec lifecycle hook ([badcommand]) for Container "lifecycle-demo-container" in Pod "lifecycle-demo_default(30229739-9651-4e5a-9a32-a8f1688862db)" failed - error: command 'badcommand' exited with 126: , message: "OCI runtime exec failed: exec failed: container_linux.go:380: starting container process caused: exec: "badcommand": executable file not found in $PATH: unknownrn" Normal   Killing              4s (x2 over 5s)  kubelet            FailedPostStartHook Normal   Pulled               4s               kubelet            Successfully pulled image "nginx" in 215.66395ms Warning  BackOff              2s (x2 over 3s)  kubelet            Back-off restarting failed container </ins> ```

This is a Feature Request What would you like to be We need to update content/ja/docs/concepts/containers/container-lifecycle- according to the English text, because it is outdated. Why is this needed content/ja/docs/concepts/containers/container-lifecycle- is outdated. Comments /language ja /assign
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


Question: --- <!-- overview --> <del> {{< feature-state state="stable" >}} </del> <ins> {{< feature-state feature_gate_name="HugePages" >}} </ins> Kubernetes supports the allocation and consumption of pre-allocated huge pages by applications in a Pod. This page describes how users can consume huge pages.

Hi, In k8s v1.30 documentation page , in the top FEATURE STATE line, the indicated Kubernetes version where this feature reached "stable/GA" is said to be 1.30; if you check which it is in k8s v1.29 doc page: it says 1.29 .... for 1.28 doc it says GA/stable was reached in 1.28 ... and so for the previous releases ... It looks there is a wrong moving version for this, pointing to the current one "owning" the doc page. According to it should say: FEATURE STATE: Kubernetes v1.14 [stable]
Page reported in issue: /language en /kind bug
We should correct this discrepancy in the feature state. /priority backlog /triage accepted
I try to help with this. /assign


Question: <del> apiVersion: apps/v1beta2 # for versions before 1.8.0 use apps/v1beta1 </del> <ins> apiVersion: apps/v1 # for versions before 1.9.0 use apps/v1beta2 </ins> kind: Deployment metadata: name: redis-master

<!-- 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: Deployment yaml file: mysql- api version does not fit 1.9 version: apiVersion: apps/v1beta2 # for versions before 1.8.0 use apps/v1beta1 kind: Deployment Proposed Solution: change apiVersion to: apps/v1 Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--Kubernetes Version: 9 ! <!--Additional Information:--


Question: } ``` <del> #### Support traffic shaping </del> <ins> ### Support traffic shaping </ins> **Experimental Feature**

! ref:
/sig node /kind cleanup If any flag found which was removed in , Kindly remove them too.
/triage accepted
/language en
For anyone facing this issue and Kubernetes is not starting, I removed the flag from file and restarted kubelet service. ().
/priority important-longterm
I have run into the same problem and removing it from does not work. Basically this breaks the system
Hi Seems like you are using . If not ,kindly share kubelet version and log. Thanks !!
The version i used was 1.24.0 from the debian repo, downgrading to 1.23.6 solved my issue and got everything running again Let me know if more information is needed?
How you have bootstrapped the cluster? Using kubeadm or different tools
I was using 1.23 and I came up with this issue upon performing updates to the nodes of the cluster (apt-get upgrade). Then, 1.24 was installed and the issue came up and I managed to resolve it as I mentioned above as the logs of the kubelet service were indicating error with the --network-plugin flag.
Behaviour is expected. since remove in v1.24 Please share and the output of ?
: Logs:
Folks, this is an accepted issue. We should update that page to remove mentions of the command line argument. Pull requests are welcome - see for tips on how to contribute.
my cluster is down after doing an apt upgrade. From what I can understand it looks like I have this issue, running version 1.24.0 as well. Is here any instructions on how to downgrade my cluster so that I can get it up and running again? Update: I’ve managed to get my cluster up and running again. Whilst I agree that this comment is off-topic for the exact problem at hand, this may help someone with the problem that I had. The problem is that my K8S install was running on docker, and now dockershim has been removed, which is what stopped my cluster working. I used a couple of posts to get the problem I was having solved. Here’s one of the link (I can’t remember the other) On the workers, I streamlined the changes to this…. The first line should prevent the problem that I had - auto upgrading k8s during an apt upgrade.

Updating to 1.24 had the breaking change that caused my cluster to become unavailable. sudo apt-mark hold kubelet kubeadm kubectl sudo systemctl enable --now kubelet sudo su - mkdir -p /etc/containerd containerd config exit sudo nano /var/lib/kubelet/kubeadm- Remove --network-plugin=cni Add --container-runtime=remote --container-runtime- Save Sudo reboot At this point the node should come up. Not 100% sure if this will solve the problem on the control plain, I got that working before streamlining the commands, anything else should be able to be taken from the link I posted above.
I got mine up by simply downgrading the kubelet to latest 1.23.x
I've marked some off-topic comments as hidden. They're not deleted (you can click Show comment to reveal them). Please, folks, do focus on the topic here: fixing the Kubernetes documentation about setting up cluster networking
If anyone has questions about how to propose a fix for , you're very welcome to ask. You can reply here or, if you use the Kubernetes workspace for Slack, ask there in the channel.
I've created a SO page to redirect all the "how to fix my cluster now" questions there: . Should I update the OP to reflect this link and state that this is not a request to fix the cluster's setup?
Duplicated by issue
We should edit so that it is no longer incorrect, and then close this issue.
Anyone who wants to edit that page is welcome to.
/assign
is reviewing PR
remove " --network-plugin"flag work fine.
This resulted in my case just in another error:
same error for me.
same here EDIT: fixed it by "migrating" from docker to containerd by simply: now connect kubelet to containerd directly by editing /etc/systemd/system/kubelet.service.d/10- add after "ExecStart=/usr/bin/kubelet" which looks like: for me. finally restart kubelet.service:
As this bug is resolved, I'm going to lock it to ensure that the record remains on-topic.


Question: <del> --- title: "Penjadwalan" weight: 90 --- </del>

This is tracking issue of our progress from Q1 2021 onwards. In the beginning of this milestone, as per our , we have translated 220 pages from 84 contributors (the script from main repo shows 260+ pages), with around 8,000 views per month. In this milestone, we still continuing on updating the obsolete pages. We are not officially listing down target pages to translate, but feel free if you have spare time to translate some. Please check this documentation about which gives step-by-step on how to start to contribute and translate using official guidelines. There is a list of outdated pages (40 out of 162 pages for this milestone) and please feel free if you want to take part on this work.

[X] removed [X] removed content/en//docs/tasks/tools/install- [X] removed [X] removed content/en//docs/tasks/example-task- [X] removed content/en//docs/tasks/administer-cluster/cluster- [X] removed content/en//docs/setup/learning- [X] removed content/en//docs/concepts/configuration/assign-pod- [X] removed content/en//docs/concepts/configuration/pod- [ ] removed content/en//docs/concepts/configuration/manage-compute-resources- [X] moved content/en//docs/concepts/configuration/resource-bin- [X] moved content/en//docs/concepts/configuration/taint-and- [X] renamed content/en//docs/concepts/scheduling/scheduling- [X] renamed content/en//docs/concepts/scheduling/scheduler-perf- [X] renamed content/en//docs/concepts/scheduling/kube- [X] renamed [ ] removed content/en//docs/concepts/workloads/pods/pod-[ ] removed [ ] removed content/en//docs/concepts/workloads/controllers/jobs-run-to- [ ] removed content/en//docs/concepts/extend-kubernetes/poseidon-firmament-alternate- [ ] removed [ ] removed content/en//docs/concepts/cluster-administration/cluster-administration- [ ] removed content/en//docs/concepts/cluster- [ ] removed content/en//docs/concepts/cluster-administration/cloud- [ ] removed content/en//docs/concepts/cluster-administration/controller-[X] removed content/en//docs/concepts/cluster- [X] removed [X] removed [X] removed [X] modified content/en/includes/task-tutorial- [X] modified content/en/docs/home/supported-doc- [ ] modified [ ] modified content/en/docs/tasks/debug-application-cluster/resource-usage-[ ] modified content/en/docs/tasks/run-application/horizontal-pod-autoscale- [ ] modified content/en/docs/tasks/run-application/horizontal-pod- [ ] modified content/en/docs/tasks/run-application/run-stateless-application- [ ] modified content/en/docs/tasks/run-application/force-delete-stateful-set- [ ] modified content/en/docs/tasks/tools/install- [ ] modified [ ] modified content/en/docs/tasks/configure-pod-container/configure-service- [ ] modified content/en/docs/tasks/configure-pod-container/configure-persistent-volume- /language id /cc
/triage accepted
I'm taking the 4th part, as I've done the in
Thanks .

it is updated.
is moved to as mentioned here
is removed and redirect to official minikube webpage , as mentioned here
The whole pages are move into including as mentioned here
The whole are removed in , I'm going to remove the directory as well as it's unused now.
is moved to via
is removed via
Just sharing a useful trick for finding related PR which delete/modified a file: e.g. The output will be similar with this: Please note the commit hash in the output (, in the case of the example above). You can use the same command to find which commit modified a file by changing the filter from to (refer to for more filters). In case of modified file, you might get multiple commit hashes, pick the latest one (contains the recent changes), or just pick ones that suit your needs. Go to, e.g., (replace with your commit hash in step 1). Find the related PR with the commit, e.g. via web UI: ! In bottom left hand corner near the branch name, in this case , you can see the PR id . Click on the link and you will be redirected to the respective PR page, then you can analyse what changes has been made and what actions needed to incorporate it to our localization.
is removed here together with others.
is removed here
Hi ... it seems this issue is automatically closed. Do you have any idea how to re-opened it?
/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
Thanks :)
/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
Hi .... I think we need to close this issue, because it has already behind the schedule. Do we need to complete all within 1-2 weeks? or we need to carry forward to next quarter?
Hi All, I have opened Q2 2021 tracking issue


Question: <ins> --- title: ConfigMaps content_template: templates/concept weight: 20 --- {{% capture overview %}} {{< glossary_definition term_id="configmap" prepend="A ConfigMap is" length="all" >}} {{< caution >}} ConfigMap does not provide secrecy or encryption. If the data you want to store are confidential, use a {{< glossary_tooltip text="Secret" term_id="secret" >}} rather than a ConfigMap, or use additional (third party) tools to keep your data private. {{< /caution >}} {{% /capture %}} {{% capture body %}} ## Motivation Use a ConfigMap for setting configuration data separately from application code. For example, imagine that you are developing an application that you can run on your own computer (for development) and in the cloud (to handle real traffic). You write the code to look in an environment variable named `DATABASE_HOST`. Locally, you set that variable to `localhost`. In the cloud, you set it to refer to a Kubernetes {{< glossary_tooltip text="Service" term_id="service" >}} that exposes the database component to your cluster. This lets you fetch a container image running in the cloud and debug the exact same code locally if needed. ## ConfigMap object A ConfigMap is an API [object](/docs/concepts/overview/working-with-objects/kubernetes-objects/) that lets you store configuration for other objects to use. Unlike most Kubernetes objects that have a `spec`, a ConfigMap has a `data` section to store items (keys) and their values. The name of a ConfigMap must be a valid [DNS subdomain name](/docs/concepts/overview/working-with-objects/names#dns-subdomain-names). ## ConfigMaps and Pods You can write a Pod `spec` that refers to a ConfigMap and configures the container(s) in that Pod based on the data in the ConfigMap. The Pod and the ConfigMap must be in the same {{< glossary_tooltip text="namespace" term_id="namespace" >}}. Here's an example ConfigMap that has some keys with single values, and other keys where the value looks like a fragment of a configuration format. ```yaml apiVersion: v1 kind: ConfigMap metadata: Name: game-demo data: # property-like keys; each key maps to a simple value player_initial_lives: 3 ui_properties_file_name: "user-interface.properties" # # file-like keys game.properties: | enemy.types=aliens,monsters player.maximum-lives=5 user-interface.properties: | color.good=purple color.bad=yellow allow.textmode=true ``` There are four different ways that you can use a ConfigMap to configure a container inside a Pod: 1. Command line arguments to the entrypoint of a container 1. Environment variables for a container 1. Add a file in read-only volume, for the application to read 1. Write code to run inside the Pod that uses the Kubernetes API to read a ConfigMap These different methods lend themselves to different ways of modeling the data being consumed. For the first three methods, the {{< glossary_tooltip text="kubelet" term_id="kubelet" >}} uses the data from the Secret when it launches container(s) for a Pod. The fourth method means you have to write code to read the Secret and its data. However, because you're using the Kubernetes API directly, your application can subscribe to get updates whenever the ConfigMap changes, and react when that happens. By accessing the Kubernetes API directly, this technique also lets you access a ConfigMap in a different namespace. Here's an example Pod that uses values from `game-demo` to configure a Pod: ```yaml apiVersion: v1 kind: Pod metadata: name: configmap-demo-pod spec: containers: - name: demo image: game.example/demo-game env: # Define the environment variable - name: PLAYER_INITIAL_LIVES # Notice that the case is different here # from the key name in the ConfigMap. valueFrom: configMapKeyRef: name: game-demo           # The ConfigMap this value comes from. key: player_initial_lives # The key to fetch. - name: UI_PROPERTIES_FILE_NAME valueFrom: configMapKeyRef: name: game-demo key: ui_properties_file_name volumeMounts: - name: config mountPath: "/config" readOnly: true volumes: # You set volumes at the Pod level, then mount them into containers inside that Pod - name: config configMap: # Provide the name of the ConfigMap you want to mount. name: game-demo ``` A ConfigMap doesn't differentiate between single line property values and multi-line file-like values. What matters how Pods and other objects consume those values. For this example, defining a volume and mounting it inside the `demo` container as `/config` creates four files: - `/config/player_initial_lives` - `/config/ui_properties_file_name` - `/config/game.properties` - `/config/user-interface.properties` If you want to make sure that `/config` only contains files with a `.properties` extension, use two different ConfigMaps, and refer to both ConfigMaps in the `spec` for a Pod. The first ConfigMap defines `player_initial_lives` and `ui_properties_file_name`. The second ConfigMap defines the files that the kubelet places into `/config`. {{< note >}} The most common way to use ConfigMaps is to configure settings for containers running in a Pod in the same namespace. You can also use a ConfigMap separately. For example, you might encounter {{< glossary_tooltip text="addons" term_id="addons" >}} or {{< glossary_tooltip text="operators" term_id="operator-pattern" >}} that adjust their behavior based on a ConfigMap. {{< /note >}} {{% /capture %}} {{% capture whatsnext %}} * Read about [Secrets](/docs/concepts/configuration/secret/). * Read [Configure a Pod to Use a ConfigMap](/docs/tasks/configure-pod-container/configure-pod-configmap/). * Read [The Twelve-Factor App](https://12factor.net/) to understand the motivation for separating code from configuration. {{% /capture %}} </ins>

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 write a new concept page: (or possibly ) If the does not work as the page overview, consider tweaking the glossary entry so that it does. Then use a Hugo shortcode. Why is this needed ConfigMap is a core object type for Kubernetes; as such, it needs documenting properly. Comments Consider using as an example for page structure. It's better to put Task-style documentation in task pages such as and then hyperlink to those from the Concept page. Also see: /docs/user-guide/configmap need more details on ConfigMap updates Actionable user-guide/configmap does not document self-updating It's unclear what happens when ConfigMap is changed Need doc on using ConfigMap updates Wanted: ConfigMap Rollout Options Doc
/language en /sig apps
/priority important-longterm
This is worth prioritizing /priority important-soon
/remove-priority important-longterm
/project Doc Sprints
/assign
/unassign
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
Still worth documenting /remove-lifecycle stale
/reopen let's collaborate on this!


Question: Podの名前と名前空間は[downward API](/docs/tasks/inject-data-application/downward-api-volume-expose-pod-information/)を通じて環境変数として利用可能です。 Pod定義からのユーザー定義の環境変数もコンテナで利用できます。 <del> Dockerイメージで静的に指定されている環境変数も同様です。 </del> <ins> コンテナイメージで静的に指定されている環境変数も同様です。 </ins> ### クラスター情報 コンテナの作成時に実行されていたすべてのサービスのリストは、環境変数として使用できます。 <del> これらの環境変数はDockerリンクの構文と一致します。 </del> <ins> このリストは、新しいコンテナのPodおよびKubernetesコントロールプレーンサービスと同じ名前空間のサービスに制限されます。 </ins> *bar* という名前のコンテナに対応する *foo* という名前のサービスの場合、以下の変数が定義されています。

This is a Feature Request What would you like to be We need to update content/ja/docs/concepts/containers/container- according to the English text, because it is outdated. Why is this needed content/ja/docs/concepts/containers/container- is outdated. Comments /language ja /assign
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


Question:
Solution

Mountain has been overseeing the company's migration to Kubernetes, using OpenShift Container Platform, Red Hat's enterprise container platform.

Mountain has been overseeing the company's migration to Kubernetes, using OpenShift Container Platform, Red Hat's enterprise container platform.

Impact

to /assign
Page related to issue: /language en
/retitle Update hyperlinks in 'Amadeus Case Study' page to utilize HTTPS instead of HTTP
Which is the page we should fix?
/triage accepted


Question:
On top of that, many of Pear Deck's customers are behind government firewalls and connect through Firebase, not Pear Deck's servers, making troubleshooting even more difficult.

The team began looking around for another solution, and finally decided in early 2016 to start moving the app from Heroku to Docker containers running on Google Kubernetes Engine, orchestrated by Kubernetes and monitored with Prometheus.

The team began looking around for another solution, and finally decided in early 2016 to start moving the app from Heroku to containers running on Google Kubernetes Engine, orchestrated by Kubernetes and monitored with Prometheus.
  {{< case-studies/quote image="/images/case-studies/peardeck/banner1.jpg" >}} "When it became clear that Google Kubernetes Engine was going to have a lot of support from Google and be a fully-managed Kubernetes platform, it seemed very obvious to us that was the way to go," says Eynon-Lynch.

ref: Some of the case studies need a bit of rewording to remove unnecessary mention of docker. Note: the case studies are HTML + CSS rather than markdown - you need to be familiar with that in order to update these! I'd reword “Docker containers” to “containers” I'd reword “Dockerize” to “containerize” I'd reword “Docker file” to “Dockerfile” I'd change “just over two years ago” to “in 2015” I'd also change “Dockerized” to “containerized” /priority backlog /triage accepted
Hi there, I would like to work on this issue. /assign
I have an question does the PR need to made against the branch or the branch? Thanks
You need to make a PR against the branch.
/good-first-issue
This request has been marked as suitable for new contributors. Please ensure that the issue body includes answers to the following questions: Why are we solving this issue? To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points? Does this issue have zero to low barrier of entry? How can the assignee reach out to you for help? For more details on the requirements of such an issue, please see and ensure that they are met. If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /good-first-issue 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
/assign
Hi I have opened a regarding this a few days ago. If you are free can you PTAL at the PR. Thanks.
Please close your PR as has already it earlier. Kindly look into those issues which are not already assigned to someone. Thank you.
/assign


Question: ``` With the MySQL `StatefulSet` and `Service` you'll notice information about both MySQL and WordPress, the broader application, are included.

The page recommends setting the label. One of the suggested values is a semver. The problem with that recommendation is that there are plenty of fully compliant semvers that are incompatible with the restrictions that k8s put on the . Including the build number, for example, will cause a runtime error:
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
/retitle Recommended Labels page suggests using SemVer when only a subset of semvers are valid A plausible fix would be to specify the version of SemVer - as I understand it, all 1.x SemVers are valid. /language en
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Mark this issue or PR as fresh with Mark this issue or PR as rotten with Close this issue or PR with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /lifecycle stale [1]:
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Mark this issue or PR as fresh with Close this issue or PR with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /lifecycle rotten [1]:
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Reopen this issue or PR with Mark this issue or PR as fresh with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /close [1]:
Closing this issue. <detailsIn response to : The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closedReopen this issue or PR with Mark this issue or PR as fresh with Offer to help out with [Issue Triage][1] 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
/reopen /lifecycle frozen /priority backlog
Reopened this issue. <detailsIn response to : /reopen /lifecycle frozen /priority backlog 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
/kind bug /help
This request has been marked as needing help from a contributor. Please ensure that the issue body includes answers to the following questions: Why are we solving this issue? To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points? Does this issue have zero to low barrier of entry? How can the assignee reach out to you for help? For more details on the requirements of such an issue, please see and ensure that they are met. If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /kind bug /help 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 guess that another option is to add notes after the table that should contain something similar to
If we can agree with text change, I can work on this
That's quite vague still, and doesn't really help in understand what is allowed. Would it make sense to mention "Semantic Versioning 1.0.0"?
I think it would. We're then explicitly declaring a version of, uh, SemVer that we can be compatible with, following the rules of that version of SemVer.
you are welcome to edit the issue description with that recommended fix, or to include a link to
Ok so we want to change the description in the table to If we agree with such wording, I can create a PR with it.
As a project, let's recommend using SemVer 1.0 We can explain that if people want to use another version scheme, they have options: use your own annotation (custom key) use different label, which means using a custom key for that I wonder if actually we should be recommending use of as an annotation, not a label. However let's not do that yet; for now, let's fix the issue where we're not specifying a suitable SemVer version, and save the bigger discussion for another time.
/assign
PR to get things started: I'm not sure how far/how we wanted to go about this - recommend using SemVer 1.0 - do we mean more so than revision, hash, etc? In which case re-word the whole line from: to Then for the explanation on custom keys, add to the bottom of the table as a footnote or something similar?
Also see


Question: CONTAINER       IMAGE                                 CREATED           STATE      NAME    ATTEMPT    POD ID f427638871c35   docker.io/library/nginx@sha256:...    19 seconds ago    Running    web     1          34533c6729106 ``` <ins> ## {{% heading "whatsnext" %}} * [Generate static Pod manifests for control plane components](/docs/reference/setup-tools/kubeadm/implementation-details/#generate-static-pod-manifests-for-control-plane-components) * [Generate static Pod manifest for local etcd](/docs/reference/setup-tools/kubeadm/implementation-details/#generate-static-pod-manifest-for-local-etcd) * [Debugging Kubernetes nodes with `crictl`](/docs/tasks/debug/debug-cluster/crictl/) * [Learn more about `crictl`](https://github.com/kubernetes-sigs/cri-tools). * [Map `docker` CLI commands to `crictl`](/docs/reference/tools/map-crictl-dockercli/). * [Set up etcd instances as static pods managed by a kubelet](/docs/setup/production-environment/tools/kubeadm/setup-ha-etcd-with-kubeadm/) </ins>

This is a Bug Report There is a section named in page, we should add log info observation for static pod as well in the page for user benefits. Also there is already a page with a section dedicated to it. I think that will be really useful. Problem: No log observation method mentioned in the Observe static pod behaviour section Proposed Solution: Add a reference link directing to in the aforementioned section 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
/assign
Would we also want to document how to work out which container ID is the right one to check?
Hi , This section might be explaining subtly how to see your container. would you like a detailed version of how this can be defined?
Hi , I already started working on this issue yesterday, is it okay if I carry forward or you want to take this up?
is a glimpse of what i in the static-pod docs Also there can be more addition to the reference section i.e. section. I some links that can be useful for understanding more about static pod.
/unassign


Question: ## Discussion <del> Connections made to local port 7000 are forwarded to port 6379 of the Pod that is running the Redis server. With this connection in place, you can use your </del> <ins> Connections made to local port 28015 are forwarded to port 27017 of the Pod that is running the MongoDB server. With this connection in place, you can use your </ins> local workstation to debug the database that is running in the Pod. {{< note >}}

uses manifests However, these files were removed in . The new example is using mongodb instead of redis, and so, the document needs to be updated overall. The page to update:
/language en
/kind bug /language en /priority backlog /triage accepted /help Thanks
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 : /kind bug /language en /priority backlog /triage accepted </details
/assign

On Forward a local port to a port on the Pod section this should be
/triage needs-information
Could you please link the page
This page
/triage accepted /kind bug /help
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 : /triage accepted /kind bug /help 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
/remove-triage needs-information
/assign


Question: * [Data encryption in transit](/docs/tasks/tls/managing-tls-in-a-cluster/) for the control plane * [Data encryption at rest](/docs/tasks/administer-cluster/encrypt-data/) * [Secrets in Kubernetes](/docs/concepts/configuration/secret/) <ins> * [Runtime class](/docs/concepts/containers/runtime-class) </ins> --> 学习了解相关的 Kubernetes 安全主题：

! Chinese page link can not open
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 zh
/assign
/kind bug


Question: ```powershell stop-service kubelet <del> curl.exe -Lo <path-to-kubelet.exe> "https://dl.k8s.io/{{< skew currentPatchVersion >}}/bin/windows/amd64/kubelet.exe" </del> <ins> curl.exe -Lo <path-to-kubelet.exe> "https://dl.k8s.io/v{{< skew currentPatchVersion >}}/bin/windows/amd64/kubelet.exe" </ins> restart-service kubelet ``` -->

<!--Required Information--Problem: We've deprecated the param () and now English documents are using instead. (by ) All the other documents need to change into or appropriatly. Since several languages are involved, I'd like to share this issue to check all localizations complete the task. Proposed Solution: For each localization team, search and change appropriately. (See the reference, ) Please check the following task box if the localization task is complete. Page to Update: [x] de [x] es [x] fr [x] hi [x] id [x] ja [x] ko [x] pt-br [x] ru [x] vi [ ] zh-ch [previously done]Once all localizations have switched over, we can remove the parameter from the site.
/assign for the Korean contents.
PR: [ko] Replace deprecated fullversion shortcode for Korean :) The task for Korean can be completed after is merged into the main branch.
/assign For Brazilian Portuguese changes
/triage accepted
/assign For Hindi changes
The Brazilian Portuguese localization has replaced all occurrences via /.
/assign for french content
/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
/remove-help
I reopened as there is one more page to fix.
Really done! Thanks folks. /close
Closing this issue. <detailsIn response to : Really done! 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


Question: `VolumeSnapshotClass` allows you to specify different attributes belonging to a `VolumeSnapshot`. These attributes may differ among snapshots taken from the same volume on the storage system and therefore cannot be expressed by using the same `StorageClass` of a `PersistentVolumeClaim`. <ins> Volume snapshots provide Kubernetes users with a standardized way to copy a volume's contents at a particular point in time without creating an entirely new volume. This functionality enables, for example, database administrators to backup databases before performing edit or delete modifications. </ins> Users need to be aware of the following when using this feature: * API Objects `VolumeSnapshot`, `VolumeSnapshotContent`, and `VolumeSnapshotClass` are {{< glossary_tooltip term_id="CustomResourceDefinition" text="CRDs" >}}, not part of the core API.

Maybe its just me, but reading the page first time it is not clear what these volume-snapshots are really good for. Reading it again doesn't help, but it makes one thing clear: Taking a snapshot is just half of the story. Maybe a practical example (e.g. backup and restore of a mysql database, migration to another cluster) would be an improvement.
Thanks for the suggestion /language en /triage accepted /sig storage /priority backlog
/assign


Question: If you try to create a Service with an invalid `clusterIP` address value, the API server will return a 422 HTTP status code to indicate that there's a problem. <del> Read [avoiding collisions](#avoiding-collisions) </del> <ins> Read [avoiding collisions](/docs/reference/networking/virtual-ips/#avoiding-collisions) </ins> to learn how Kubernetes helps reduce the risk and impact of two different Services both trying to use the same IP address.

This is a Bug Report Problem: Links for Avoiding collisions are broken in: (at point) Proposed Solution: Update in both pages with Other possible solutions: Page to Update:
/language en /area blog
/retitle Broken links for "Avoiding collisions" in 'Service' and 'Feature Gates' page /remove-area blog
I think the link became broken during the revision process of the Service concept page. We should make an update to direct it to the correct location, which I believe is /priority backlog /triage accepted
/assign
/sig docs PR raised
Similar to


Question: ```shell <del> # Change redis-master-765d459796-258hz to the name of the Pod kubectl port-forward redis-master-765d459796-258hz 7000:6379 </del> <ins> # Change mongo-75f59d57f4-4nd6q to the name of the Pod kubectl port-forward mongo-75f59d57f4-4nd6q 28015:27017 </ins> ``` which is the same as ```shell <del> kubectl port-forward pods/redis-master-765d459796-258hz 7000:6379 </del> <ins> kubectl port-forward pods/mongo-75f59d57f4-4nd6q 28015:27017 </ins> ``` or ```shell <del> kubectl port-forward deployment/redis-master 7000:6379 </del> <ins> kubectl port-forward deployment/mongo 28015:27017 </ins> ``` or ```shell <del> kubectl port-forward replicaset/redis-master 7000:6379 </del> <ins> kubectl port-forward replicaset/mongo-75f59d57f4 28015:27017 </ins> ``` or ```shell <del> kubectl port-forward service/redis-master 7000:redis </del> <ins> kubectl port-forward service/mongo 28015:27017 </ins> ``` Any of the above commands works. The output is similar to this: ``` <del> Forwarding from 127.0.0.1:7000 -> 6379 Forwarding from [::1]:7000 -> 6379 </del> <ins> Forwarding from 127.0.0.1:28015 -> 27017 Forwarding from [::1]:28015 -> 27017 </ins> ``` {{< note >}}

uses manifests However, these files were removed in . The new example is using mongodb instead of redis, and so, the document needs to be updated overall. The page to update:
/language en
/kind bug /language en /priority backlog /triage accepted /help Thanks
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 : /kind bug /language en /priority backlog /triage accepted </details
/assign

On Forward a local port to a port on the Pod section this should be
/triage needs-information
Could you please link the page
This page
/triage accepted /kind bug /help
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 : /triage accepted /kind bug /help 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
/remove-triage needs-information
/assign


Question: color: #fff; background: #326de6; } <ins> // Adjust Bing search result page #bing-results-container { padding: 1em; } #bing-pagination-container { padding: 1em; margin-bottom: 1em; a.bing-page-anchor { padding: 0.5em; margin: 0.25em; } } </ins>

In Kubernetes docs when you search, search results page number displays as "". There is no space between page numbers. The commit message appears at the bottom of the page which is irrelevant. Also, the hyperlink appears in each search results which is not needed. eg: Expected Output. Search results in a proper way.
/language en Sounds like 3 different issues, :)
Can you clarify the issue(s) you're reporting If you can include a screenshot that's helpful; if you can open a new issue for each separate defect that's even better.
This problem happens when using Bing search. Here is the screenshot: !
/area web-development For context, the website uses Google Search unless corporate filtering / state-level censorship / similar restrictions prevent using Google, and for those readers there is a fallback to Bing search.
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
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 rotten I'm going to create a PR to fix this styling issue.
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-contributor-experience at . /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-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
/triage accepted /lifecycle frozen
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
It took a long time but I made a PR to fix this issue.


Question: ```bash echo 'source <(kubectl completion bash)' >>~/.bashrc ``` - Add the completion script to the `/etc/bash_completion.d` directory: ```bash kubectl completion bash >/etc/bash_completion.d/kubectl ``` If you have an alias for kubectl, you can extend shell completion to work with that alias: ```bash

There are no details or instructions on how to validate the binary downloaded from this page via some form of checksum, sha256 or otherwise. For automation purposes, eg. ansible playbook, being able to validate any binary downloads is a requirement of project stakeholders.
The site doesn't allow browsing, but the file is there as kubectl.sha256 afterall. Might be worth mentioning this in the document?
/retitle Document how to validate kubectl binary against checksum / signature /language en /kind feature /triage accepted The page in question is
To fix this: update to use download links from for example also explain to readers that checksum files are available that they can use to compare binaries obtained from elsewhere for example The and shortcodes are useful for automatically filling in the current Kubernetes version. /help /sig cli
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 : To fix this: update to use download links from explain to readers that checksum files are available that they can use to compare binaries obtained from elsewhere /sig cli 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 may be able to help with this /assign


Question: is enabled on the API server. An administrator can mark a specific `StorageClass` as default by adding the <del> `storageclass.kubernetes.io/is-default-class` annotation to it. </del> <ins> `storageclass.kubernetes.io/is-default-class` [annotation](/docs/reference/labels-annotations-taints/#storageclass-kubernetes-io-is-default-class) to it. </ins> When a default `StorageClass` exists in a cluster and a user creates a `PersistentVolumeClaim` with `storageClassName` unspecified, the `DefaultStorageClass` admission controller automatically adds the

When enabling dynamic provisioning as default behaviour: It might be helpful to reference the following as a hyper link for clarity
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
/kind feature /language en It sounds as if we could add a hyperlink from to and that would solve it for you Have I got that right?
Hi Tim, I would agree this would be awesome for users. Kind regards Naresh Maharaj
would you be willing to update (edit) the issue description, with in mind, so that it's clear what change you are asking for?
/sig storage
/assign


Question: db-user-pass-96mffmfh4k          Opaque                                2         51s ``` <ins> You can view a description of the secret: </ins> ```shell kubectl describe secrets/db-user-pass-96mffmfh4k ```

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: Line 355: There is no description before the code. Line 1005: There is no description before the code. Proposed Solution: Line 355: You can view a description of the secret: Line 1005: You can also create a secret for test environment credentials. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language en
/assign