Question: <ins> <?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Do not edit this file with editors other than draw.io --> <svg 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);" id="svg29" sodipodi:docname="flowchart.svg" inkscape:version="1.3-beta (cedbd6c6ff, 2023-05-28)" xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape" xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg"> <sodipodi:namedview id="namedview29" pagecolor="#ffffff" bordercolor="#000000" borderopacity="0.25" inkscape:showpageshadow="2" inkscape:pageopacity="0.0" inkscape:pagecheckerboard="0" inkscape:deskcolor="#d1d1d1" inkscape:zoom="1.4796238" inkscape:cx="376.44703" inkscape:cy="290.95233" inkscape:window-width="1920" inkscape:window-height="1137" inkscape:window-x="-8" inkscape:window-y="-8" inkscape:window-maximized="1" inkscape:current-layer="g28" /> <defs id="defs1" /> <g id="g28"> <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" id="path1" /> <ellipse cx="77.35" cy="52.5" rx="47.25" ry="31.499999999999996" fill="#454545" stroke="none" pointer-events="all" id="ellipse1" /> <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" id="path2" /> <rect x="0.35" y="133" width="154" height="42" fill="#ffffff" stroke="#000000" stroke-width="1.05" pointer-events="all" id="rect2" /> <rect x="252.79" y="31.94" width="100.63" height="41.13" fill="none" stroke="none" pointer-events="all" id="rect3" /> <g transform="translate(-0.5 -0.5)scale(0.7)" id="g3"> <text xml:space="preserve" style="font-size:15.2381px;font-family:sans-serif;-inkscape-font-specification:sans-serif;fill:#9ce8fc;stroke-width:1.42857" x="432.02502" y="71.00174" id="text30"><tspan sodipodi:role="line" id="tspan29" style="font-size:15.2381px;text-align:center;text-anchor:middle;fill:#ffffff;stroke-width:1.42857" x="432.02502" y="71.00174">你是否想要在 Kubernetes API</tspan><tspan sodipodi:role="line" style="font-size:15.2381px;text-align:center;text-anchor:middle;fill:#ffffff;stroke-width:1.42857" x="432.02502" y="90.433144" id="tspan30">中添加全新的类别？</tspan></text> </g> <g transform="matrix(0.7,0,0,0.7,341.57579,125.42893)" id="g3-3"> <text xml:space="preserve" style="font-size:15.2381px;font-family:sans-serif;-inkscape-font-specification:sans-serif;fill:#9ce8fc;stroke-width:1.42857" x="418.37085" y="110.25751" id="text30-2"><tspan sodipodi:role="line" style="font-size:15.2381px;text-align:center;text-anchor:middle;fill:#ffffff;stroke-width:1.42857" x="418.37085" y="110.25751" id="tspan30-5">你是否想要限制或自动编辑</tspan><tspan sodipodi:role="line" style="font-size:15.2381px;text-align:center;text-anchor:middle;fill:#ffffff;stroke-width:1.42857" x="418.37085" y="129.68892" id="tspan31">某些或所有 API 类别的字段？</tspan></text> </g> <ellipse cx="630.35" cy="52.51" rx="47.25" ry="31.499999999999996" fill="#454545" stroke="none" pointer-events="all" id="ellipse3" /> <rect x="564.07" y="189" width="152.03" height="35" fill="none" stroke="none" pointer-events="all" id="rect4" /> <ellipse cx="448.35" cy="206.5" rx="47.25" ry="31.499999999999996" fill="#454545" stroke="none" pointer-events="all" id="ellipse5" /> <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" id="path6" /> <rect x="371.35" y="280" width="154" height="42" fill="#ffffff" stroke="#000000" stroke-width="1.05" pointer-events="all" id="rect6" /> <ellipse cx="630.35" cy="311.5" rx="47.25" ry="31.499999999999996" fill="#454545" stroke="none" pointer-events="all" id="ellipse7" /> <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" id="path8" /> <rect x="555.1" y="399" width="169.75" height="35" fill="none" stroke="none" pointer-events="all" id="rect8" /> <ellipse cx="420.35" cy="416.5" rx="47.25" ry="31.499999999999996" fill="#454545" stroke="none" pointer-events="all" id="ellipse9" /> <ellipse cx="586.6" cy="528.5" rx="47.25" ry="31.499999999999996" fill="#454545" stroke="none" pointer-events="all" id="ellipse10" /> <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" id="path11" /> <ellipse cx="742.35" cy="528.5" rx="47.25" ry="31.499999999999996" fill="#454545" stroke="none" pointer-events="all" id="ellipse11" /> <ellipse cx="254.1" cy="528.5" rx="47.25" ry="31.499999999999996" fill="#454545" stroke="none" pointer-events="all" id="ellipse12" /> <rect x="356.47" y="504" width="177.63" height="49" fill="none" stroke="none" pointer-events="all" id="rect13" /> <rect x="177.1" y="595" width="154" height="42" fill="#ffffff" stroke="#000000" stroke-width="1.05" pointer-events="all" id="rect14" /> <rect x="509.6" y="595" width="154" height="42" fill="#ffffff" stroke="#000000" stroke-width="1.05" pointer-events="all" id="rect15" /> <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" id="path16" /> <path d="M 77.35 133 L 77.35 84" fill="none" stroke="#000000" stroke-width="0.7" stroke-miterlimit="10" pointer-events="stroke" id="path17" /> <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" id="path18" /> <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" id="path19" /> <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" id="path20" /> <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" id="path21" /> <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" id="path22" /> <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" id="path23" /> <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" id="path24" /> <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" id="path25" /> <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" id="path26" /> <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" id="path27" /> <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" id="path28" /> <g id="g1-5" transform="translate(-0.94906787,208.10827)"> <g transform="matrix(0.7,0,0,0.7,341.57579,125.42893)" id="g3-3-5"> <text xml:space="preserve" style="font-size:15.2381px;font-family:sans-serif;-inkscape-font-specification:sans-serif;fill:#9ce8fc;stroke-width:1.42857" x="415.47437" y="113.63674" id="text30-2-8"><tspan sodipodi:role="line" style="font-size:15.2381px;text-align:center;text-anchor:middle;fill:#ffffff;stroke-width:1.42857" x="415.47437" y="113.63674" id="tspan31-9">你是否想要更改内置</tspan><tspan sodipodi:role="line" style="font-size:15.2381px;text-align:center;text-anchor:middle;fill:#ffffff;stroke-width:1.42857" x="415.47437" y="133.06816" id="tspan34">API 类别的底层实现？</tspan></text> </g> </g> <g id="g1-5-4" transform="translate(-212.80121,318.9108)"> <g transform="matrix(0.7,0,0,0.7,341.57579,125.42893)" id="g3-3-5-2"> <text xml:space="preserve" style="font-size:15.2381px;font-family:sans-serif;-inkscape-font-specification:sans-serif;fill:#9ce8fc;stroke-width:1.42857" x="416.92261" y="107.84377" id="text30-2-8-9"><tspan sodipodi:role="line" style="font-size:15.2381px;text-align:center;text-anchor:middle;fill:#ffffff;stroke-width:1.42857" x="416.92261" y="107.84377" id="tspan34-4">你是否想要更改 Volume、</tspan><tspan sodipodi:role="line" style="font-size:15.2381px;text-align:center;text-anchor:middle;fill:#ffffff;stroke-width:1.42857" x="416.92261" y="128.373" id="tspan36">Service、Ingress、PersistentVolume？</tspan></text> </g> </g> <text xml:space="preserve" style="font-size:10.6667px;font-family:sans-serif;-inkscape-font-specification:sans-serif;text-align:center;text-anchor:middle;fill:#ffffff" x="76.546616" y="56.609112" id="text37"><tspan sodipodi:role="line" id="tspan37" x="76.546616" y="56.609112">是</tspan></text> <text xml:space="preserve" style="font-size:10.6667px;font-family:sans-serif;-inkscape-font-specification:sans-serif;text-align:center;text-anchor:middle;fill:#ffffff" x="450.05069" y="210.53658" id="text37-5"><tspan sodipodi:role="line" id="tspan37-8" x="450.05069" y="210.53658">是</tspan></text> <text xml:space="preserve" style="font-size:10.6667px;font-family:sans-serif;-inkscape-font-specification:sans-serif;text-align:center;text-anchor:middle;fill:#ffffff" x="419.82144" y="418.95734" id="text37-2"><tspan sodipodi:role="line" id="tspan37-4" x="419.82144" y="418.95734">是</tspan></text> <text xml:space="preserve" style="font-size:10.6667px;font-family:sans-serif;-inkscape-font-specification:sans-serif;text-align:center;text-anchor:middle;fill:#ffffff" x="631.0235" y="313.58737" id="text37-2-4"><tspan sodipodi:role="line" id="tspan37-4-6" x="631.0235" y="313.58737">否</tspan></text> <text xml:space="preserve" style="font-size:10.6667px;font-family:sans-serif;-inkscape-font-specification:sans-serif;text-align:center;text-anchor:middle;fill:#ffffff" x="254.47926" y="534.35229" id="text37-55"><tspan sodipodi:role="line" id="tspan37-40" x="254.47926" y="534.35229">是</tspan></text> <text xml:space="preserve" style="font-size:10.6667px;font-family:sans-serif;-inkscape-font-specification:sans-serif;text-align:center;text-anchor:middle;fill:#ffffff" x="633.18011" y="57.422901" id="text37-2-4-4"><tspan sodipodi:role="line" id="tspan37-4-6-8" x="633.18011" y="57.422901">否</tspan></text> <text xml:space="preserve" style="font-size:10.6667px;font-family:sans-serif;-inkscape-font-specification:sans-serif;text-align:center;text-anchor:middle;fill:#ffffff" x="585.76648" y="532.07996" id="text37-2-4-46"><tspan sodipodi:role="line" id="tspan37-4-6-1" x="585.76648" y="532.07996">否</tspan></text> <text xml:space="preserve" style="font-size:10.6667px;font-family:sans-serif;-inkscape-font-specification:sans-serif;text-align:center;text-anchor:middle;fill:#ffffff" x="742.38641" y="531.4621" id="text37-2-4-8"><tspan sodipodi:role="line" id="tspan37-4-6-3" x="742.38641" y="531.4621">否</tspan></text> <text xml:space="preserve" style="font-size:8px;font-family:sans-serif;-inkscape-font-specification:sans-serif;text-align:center;text-anchor:middle;fill:#ffffff" x="80.742378" y="156.72789" id="text38"><tspan sodipodi:role="line" id="tspan38" x="80.742378" y="156.72789" style="font-size:8px;fill:#000000">转到“API Extensions”</tspan></text> <text xml:space="preserve" style="font-size:8px;font-family:sans-serif;-inkscape-font-specification:sans-serif;text-align:center;text-anchor:middle;fill:#ffffff" x="451.74719" y="303.39474" id="text38-9"><tspan sodipodi:role="line" id="tspan38-5" x="451.74719" y="303.39474" style="font-size:8px;fill:#000000">转到“API Access Extensions”</tspan></text> <text xml:space="preserve" style="font-size:8px;font-family:sans-serif;-inkscape-font-specification:sans-serif;text-align:center;text-anchor:middle;fill:#ffffff" x="253.34416" y="618.552" id="text38-7"><tspan sodipodi:role="line" id="tspan38-7" x="253.34416" y="618.552" style="font-size:8px;fill:#000000">转到“Infrastructure”</tspan></text> <text xml:space="preserve" style="font-size:8px;font-family:sans-serif;-inkscape-font-specification:sans-serif;text-align:center;text-anchor:middle;fill:#ffffff" x="594.18701" y="619.79028" id="text38-7-8"><tspan sodipodi:role="line" id="tspan38-7-6" x="594.18701" y="619.79028" style="font-size:8px;fill:#000000">转到“Automation”</tspan></text> </g> <switch id="switch29"> <g requiredFeatures="http://www.w3.org/TR/SVG11/feature#Extensibility" id="g29" /> <a transform="translate(0,-5)" xlink:href="https://www.drawio.com/doc/faq/svg-export-text-problems" target="_blank" id="a29"> <text text-anchor="middle" font-size="10px" x="50%" y="100%" id="text29">Text is not SVG - cannot display</text> </a> </switch> </svg> </ins>

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
Please raise the issue in English language so that it can be easy to understand in community.
/language zh Issue Translation is Currently this After this page select , the text in the flow chart is not .
/triage needs-information Even with a translation, I don't understand if this is a bug report, a support query, or a feature request.
/retitle [zh] Bug - the text in the flowchart should be Chinese on Extending Kubernetes page It is a bug, on zh-cn page , the text in the flowchart should be Chinese instead of Korean.
Re-titling can only be requested by trusted users, like repository collaborators. <detailsIn response to : /retitle [zh] Bug - the text in the flowchart should be Chinese on Extending Kubernetes page , the text in the flowchart should be Chinese instead of Korean. 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
/retitle [zh] Bug - the text in the flowchart should be Chinese on Extending Kubernetes page
/assign


Question: ephemeral-storage: "2Gi" limits: ephemeral-storage: "4Gi" <ins> volumeMounts: - name: ephemeral mountPath: "/tmp" volumes: - name: ephemeral emptyDir: {} </ins> ``` ### How Pods with ephemeral-storage requests are scheduled

Looking at section: Local Ephemeral Storage The example YAML for ephemeral storage does not demonstrate the need for the volume or volume mount, it only shows the resource request form in the YAML as: From reading that documentation it's easy to assume that simply adding the resource request makes that amount of storage available to the containers root filesystem, which is not correct. The ephemeral-storage volume needs to be mounted as with: and But that is not captured in the documentation. At a minimum, the example YAML should include the volume and mount example to clarify this point. Otherwise, people (like me) will unwittingly assume they have 2Gi of space on the container root, which will likely work until a random unlucky day in the future leading to hard to debug issues.
Are you okay to close this now?
/language en
I think the best way to express that is to simply add the volume mounts to the example. This example is lacking volume mounts and so it's not clear unless you dig into the text to understand this detail. If you change that example to this it becomes a complete example in which the ephemeral-storage is actually mounted. As-is that example misleads the user to thinking that they have requested 2Gi of ephemerial-storage which is applied to their root filesystem.
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
/triage accepted /language en
/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 : /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
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
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
/assign
Rotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . Send feedback to sig-contributor-experience at . /close
Closing this issue. <detailsIn response to : Rotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . /close Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/reopen
You can't reopen an issue/PR unless you authored it or you are a collaborator. <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
/reopen /remove-lifecycle rotten
Reopened this issue. <detailsIn response to : /reopen /remove-lifecycle rotten 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: <!-- image source: https://docs.google.com/drawings/d/1k2YdJgNTtNfW7_A8moIIkij-DmVgEhNrn3y2OODwqQQ/view --> <del> {{< figure src="/docs/concepts/extend-kubernetes/extension-points.svg" </del> <ins> {{< figure src="/docs/concepts/extend-kubernetes/extension-points.png" </ins> alt="用符号表示的七个编号的 Kubernetes 扩展点" class="diagram-large" caption="Kubernetes 扩展点" >}}

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
Please raise the issue in English language so that it can be easy to understand in community.
/language zh Issue Translation is Currently this After this page select , the text in the flow chart is not .
/triage needs-information Even with a translation, I don't understand if this is a bug report, a support query, or a feature request.
/retitle [zh] Bug - the text in the flowchart should be Chinese on Extending Kubernetes page It is a bug, on zh-cn page , the text in the flowchart should be Chinese instead of Korean.
Re-titling can only be requested by trusted users, like repository collaborators. <detailsIn response to : /retitle [zh] Bug - the text in the flowchart should be Chinese on Extending Kubernetes page , the text in the flowchart should be Chinese instead of Korean. 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
/retitle [zh] Bug - the text in the flowchart should be Chinese on Extending Kubernetes page
/assign


Question: the threshold values respectively. {{< /note >}} <ins> The `imagefs` is an optional filesystem that container runtimes use to store container images and container writable layers. </ins> ## Start a kubelet process configured via the config file {{< note >}}

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: As we know that, in eviction hard thresholds, when we change the default value of any one of the four parameters (memory.available, nodefs.available, imagefs.available, nodefs.inodesFree), then the value of other parameters will be set to 0. Although this is an expected behaviour but I think it's not a good motivation for user to change only the one parameter as given in this . As setting other parameters to 0 is not a good scenario. Proposed Solution: Is there any good case by setting the other parameters to 0 or we should change the example to motivate users to change all parameters Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/language en
/retitle Enhance and add more evictionHard thresholds in example yaml to encourage holistic parameter changes
/remove-kind bug /kind feature
/assign


Question: title: 代码贡献者（Code Contributor） id: code-contributor date: 2018-04-12 <del> full_link: /docs/community/devel/ </del> <ins> full_link: https://github.com/kubernetes/community/tree/master/contributors/devel </ins> short_description: > 为 Kubernetes 开源代码库开发并贡献代码的人。

This is a Bug Report I have fixed the same issue in English docs, same issue is followed by the other localization team. has one broken issue which needs to fix. ! Refer my merged PR of english docs. /assign
/triage accepted


Question: We now consider kubeadm to have achieved GA-level maturity in each of these important domains: * **Stable command-line UX** --- The kubeadm CLI conforms to [#5a GA rule of the Kubernetes Deprecation Policy](/docs/reference/using-api/deprecation-policy/#deprecating-a-flag-or-cli), which states that a command or flag that exists in a GA version must be kept for at least 12 months after deprecation. <del> * **Stable underlying implementation** --- kubeadm now creates a new Kubernetes cluster using methods that shouldn't change any time soon. The control plane, for example, is run as a set of static Pods, bootstrap tokens are used for the [`kubeadm join`](/docs/reference/setup-tools/kubeadm/kubeadm-join/) flow, and [ComponentConfig](https://github.com/kubernetes/enhancements/blob/master/keps/sig-cluster-lifecycle/wgs/0014-20180707-componentconfig-api-types-to-staging.md) is used for configuring the [kubelet](/docs/reference/command-line-tools-reference/kubelet/). </del> <ins> * **Stable underlying implementation** --- kubeadm now creates a new Kubernetes cluster using methods that shouldn't change any time soon. The control plane, for example, is run as a set of static Pods, bootstrap tokens are used for the [`kubeadm join`](/docs/reference/setup-tools/kubeadm/kubeadm-join/) flow, and [ComponentConfig](https://github.com/kubernetes/enhancements/blob/master/keps/sig-cluster-lifecycle/wgs/115-componentconfig) is used for configuring the [kubelet](/docs/reference/command-line-tools-reference/kubelet/). </ins> * **Configuration file schema** --- With the new **v1beta1** API version, you can now tune almost every part of the cluster declaratively and thus build a "GitOps" flow around kubeadm-built clusters. In future versions, we plan to graduate the API to version **v1** with minimal changes (and perhaps none). * **The "toolbox" interface of kubeadm** --- Also known as **phases**. If you don't want to perform all [`kubeadm init`](/docs/reference/setup-tools/kubeadm/kubeadm-init/) tasks, you can instead apply more fine-grained actions using the `kubeadm init phase` command (for example generating certificates or control plane [Static Pod](/docs/tasks/administer-cluster/static-pod/) manifests). * **Upgrades between minor versions** --- The [`kubeadm upgrade`](/docs/reference/setup-tools/kubeadm/kubeadm-upgrade/) command is now fully GA. It handles control plane upgrades for you, which includes upgrades to [etcd](https://etcd.io), the [API Server](/docs/reference/using-api/api-overview/), the [Controller Manager](/docs/reference/command-line-tools-reference/kube-controller-manager/), and the [Scheduler](/docs/reference/command-line-tools-reference/kube-scheduler/). You can seamlessly upgrade your cluster between minor or patch versions (e.g. v1.12.2 -> v1.13.1 or v1.13.1 -> v1.13.3).

This is a Bug Report Problem: The reference link under page is leading to 404-page not found. Proposed Solution: We should update the existing link of to the correct reference link. Page to Update:
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/language en /area blog /assign


Question: この時点で、オブジェクトはKubernetesAPIに表示されなくなります。 フォアグラウンドカスケード削除中に、オーナーの削除をブロックする依存関係は、`ownerReference.blockOwnerDeletion=true`フィールドを持つ依存関係のみです。 <del> 詳細については、[フォアグラウンドカスケード削除の使用](/docs/tasks/administer-cluster/use-cascading-deletion/#use-foreground-cascading-deletion)を参照してください。 </del> <ins> 詳細については、[フォアグラウンドカスケード削除の使用](/ja/docs/tasks/administer-cluster/use-cascading-deletion/#use-foreground-cascading-deletion)を参照してください。 </ins> ### バックグラウンドカスケード削除 {#background-deletion} バックグラウンドカスケード削除では、Kubernetes APIサーバーがオーナーオブジェクトをすぐに削除し、コントローラーがバックグラウンドで依存オブジェクトをクリーンアップします。 デフォルトでは、フォアグラウンド削除を手動で使用するか、依存オブジェクトを孤立させることを選択しない限り、Kubernetesはバックグラウンドカスケード削除を使用します。 <del> 詳細については、[バックグラウンドカスケード削除の使用](/docs/tasks/administer-cluster/use-cascading-deletion/#use-background-cascading-deletion)を参照してください。 </del> <ins> 詳細については、[バックグラウンドカスケード削除の使用](/ja/docs/tasks/administer-cluster/use-cascading-deletion/#use-background-cascading-deletion)を参照してください。 </ins> ### 孤立した依存関係 Kubernetesがオーナーオブジェクトを削除すると、残された依存関係は*orphan*オブジェクトと呼ばれます。 <del> デフォルトでは、Kubernetesは依存関係オブジェクトを削除します。この動作をオーバーライドする方法については、[オーナーオブジェクトと孤立した依存関係の削除](/docs/tasks/administer-cluster/use-cascading-deletion/#set-orphan-deletion-policy)を参照してください。 </del> <ins> デフォルトでは、Kubernetesは依存関係オブジェクトを削除します。この動作をオーバーライドする方法については、[オーナーオブジェクトの削除と従属オブジェクトの孤立](/ja/docs/tasks/administer-cluster/use-cascading-deletion/#set-orphan-deletion-policy)を参照してください。 </ins> ## 未使用のコンテナとイメージのガベージコレクション {#containers-images}

This is a Feature Request What would you like to be Translate tasks/administer-cluster/use-cascading-deletion/ into Japanese. Why is this needed This page has not been translated. 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: <!-- Fetch release_binaries.json from kubernetes-sigs/downloadkubernetes to render in table --> <del> {{ $response := getJSON "https://raw.githubusercontent.com/kubernetes-sigs/downloadkubernetes/master/dist/release_binaries.json" }} </del> <ins> {{- $url := "https://raw.githubusercontent.com/kubernetes-sigs/downloadkubernetes/master/dist/release_binaries.json" }} {{- $response := "" }} {{- with resources.GetRemote $url -}} {{- if .Err -}} {{- $message := printf "Failed to retrieve release binaries data: %s" .Err -}} {{- if eq hugo.Environment "production" -}} {{- errorf $message -}} {{- else -}} {{- warnf $message -}} {{- end -}} {{- else -}} {{- $response = .Content | transform.Unmarshal }} {{- end -}} {{- else -}} {{ $message := printf "Unable to fetch release binaries data from the specified URL: %q" $url -}} {{- if eq hugo.Environment "production" -}} {{- errorf $message -}} {{- else -}} {{- warnf $message -}} {{- end -}} {{- end -}} <!-- Continue processing only if release binaries JSON is available, accommodating for offline builds. --> {{ if ne $response nil }} </ins> {{ $currentVersion := site.Params.version }} {{ $Binaries := slice }}

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 Migrate to instead of Hugo's Why is this needed Upstream Hugo has deprecated , which we use. We should aim to migrate to use ; see Comments We may need to upgrade to a newer Hugo as part of this work, or related to it. /area web-development /lifecycle frozen
/triage accepted /priority backlog
Let me see if I can assist with this. Edit: Proposed fix in /assign


Question: admission controller. To get started with `cosigned` here are a few helpful resources: <del> * [Installation](https://github.com/sigstore/helm-charts/tree/main/charts/cosigned) </del> <ins> * [Installation](https://github.com/sigstore/cosign#installation) </ins> * [Configuration Options](https://github.com/sigstore/cosign/tree/main/config)

The and link in the section are broken.
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
I don't know if the issue is open or not, but I would like to work in it.
Looks like installation of cosign has moved from to
/assign
What about Configuration link?
Hi Instead of Configuration we can add Detailed usage of cosign there -


Question: 1. Laden Sie die neueste Version mit dem Befehl herunter: ``` <del> curl -LO https://storage.googleapis.com/kubernetes-release/release/$(curl -s https://storage.googleapis.com/kubernetes-release/release/stable.txt)/bin/linux/amd64/kubectl </del> <ins> curl -LO https://dl.k8s.io/release/$(curl -LS https://dl.k8s.io/release/stable.txt)/bin/linux/amd64/kubectl </ins> ``` <del> Um eine bestimmte Version herunterzuladen, ersetzen Sie den Befehlsteil `$(curl -s https://storage.googleapis.com/kubernetes-release/release/stable.txt)` mit der jeweiligen Version. </del> <ins> Um eine bestimmte Version herunterzuladen, ersetzen Sie den Befehlsteil `$(curl -LS https://dl.k8s.io/release/stable.txt)` mit der jeweiligen Version. </ins> Um beispielsweise die Version {{< param "fullversion" >}} auf Linux herunterzuladen, verwenden Sie den folgenden Befehl: ``` <del> curl -LO https://storage.googleapis.com/kubernetes-release/release/{{< param "fullversion" >}}/bin/linux/amd64/kubectl </del> <ins> curl -LO https://dl.k8s.io/release/{{< param "fullversion" >}}/bin/linux/amd64/kubectl </ins> ``` 2. Machen Sie die kubectl-Binärdatei ausführbar.

This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: There are still references to instead of is the correct advertised download host and will eventually move to be fastly shielding a fully community-owned bucket ref: Proposed Solution: Replace with Also replace any references with using if applicable. Page to Update: Assorted e.g. , <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/assign
hi Not a problem, didn't see anyone assigned to this issue. I am unassigning myself and assigning it to you. /unassign
/assign
Hi, I found a small issue with your proposed changes regarding one of the URLs, which is mentioned twice in the file. While returns as expected, I am getting an nginx-rendered HTML page saying for the new command () instead. As I understand, it happens due to the redirect configured on the new web server. Thus, works fine for me (it returns as expected).
i see Let me update it, thanks your work
Just done, please review all of PRs
Thanks!
And yes: These will need to follow redirects, in the future the tentative plan is it will redirect to a CDN in front of a different bucket created in a fully project / SIG-K8s-Infra controlled GCP or AWS account. I would recommend for downloading with curl more generally, even in docs / usage for other hosts.


Question: <ins> --- assignees: - eparis - pmorie title: Configuring Redis using a ConfigMap --- {% capture overview %} This page provides a real world example of how to configure Redis using a ConfigMap and builds upon the [Using ConfigMap Data in Pods](/docs/tasks/configure-pod-container/configure-pod-configmap/) and [Configure Containers Using a ConfigMap](/docs/tasks/configure-pod-container/configmap/) tasks. {% endcapture %} {% capture objectives %} * Create a ConfigMap. * Create a pod specification using the ConfigMap. * Create the pod. * Verify that the configuration was correctly applied. {% endcapture %} {% capture prerequisites %} * {% include task-tutorial-prereqs.md %} * Understand [Using ConfigMap Data in Pods](/docs/tasks/configure-pod-container/configure-pod-configmap/). * Understand [Configure Containers Using a ConfigMap](/docs/tasks/configure-pod-container/configmap/). {% endcapture %} {% capture lessoncontent %} ## Real World Example: Configuring Redis using a ConfigMap You can follow the steps below to configure a Redis cache using data stored in a ConfigMap. 1. Create a ConfigMap from the `docs/user-guide/configmap/redis/redis-config` file: ```shell kubectl create configmap example-redis-config --from-file=docs/user-guide/configmap/redis/redis-config kubectl get configmap example-redis-config -o yaml ``` ```yaml apiVersion: v1 data: redis-config: | maxmemory 2mb maxmemory-policy allkeys-lru kind: ConfigMap metadata: creationTimestamp: 2016-03-30T18:14:41Z name: example-redis-config namespace: default resourceVersion: "24686" selfLink: /api/v1/namespaces/default/configmaps/example-redis-config uid: 460a2b6e-f6a3-11e5-8ae5-42010af00002 ``` 1. Create a pod specification that uses the config data stored in the ConfigMap: ```yaml apiVersion: v1 kind: Pod metadata: name: redis spec: containers: - name: redis image: kubernetes/redis:v1 env: - name: MASTER value: "true" ports: - containerPort: 6379 resources: limits: cpu: "0.1" volumeMounts: - mountPath: /redis-master-data name: data - mountPath: /redis-master name: config volumes: - name: data emptyDir: {} - name: config configMap: name: example-redis-config items: - key: redis-config path: redis.conf ``` 1. Create the pod: ```shell kubectl create -f docs/user-guide/configmap/redis/redis-pod.yaml ``` In the example, the config volume is mounted at `/redis-master`. It uses `path` to add the `redis-config` key to a file named `redis.conf`. The file path for the redis config, therefore, is `/redis-master/redis.conf`. This is where the image will look for the config file for the redis master. 1. Use `kubectl exec` to enter the pod and run the `redis-cli` tool to verify that the configuration was correctly applied: ```shell kubectl exec -it redis redis-cli 127.0.0.1:6379> CONFIG GET maxmemory 1) "maxmemory" 2) "2097152" 127.0.0.1:6379> CONFIG GET maxmemory-policy 1) "maxmemory-policy" 2) "allkeys-lru" ``` {% endcapture %} {% capture whatsnext %} * Learn more about [ConfigMaps](/docs/tasks/configure-pod-container/configmap/). * See [Using ConfigMap Data in Pods](/docs/tasks/configure-pod-container/configure-pod-configmap). {% endcapture %} {% include templates/tutorial.md %} </ins>

<!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!--Required Information--This is a... [x ] Feature Request Problem: As discussed in , the 'Real World Example' section of should probably be a separate tutorial. Proposed Solution: Create a new tutorial from the existing content (probably needs additional information). Remove the section from the task doc and replace with a 'What's Next' pointer to new tutorial doc. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
done


Question: ## {{% heading "whatsnext" %}} - [Pengelolaan Objek Kubernetes Menggunakan Perintah Imperatif](/id/docs/tasks/manage-kubernetes-objects/imperative-command/) <del> - [Pengelolaan Objek Kubernetes secara Imperatif Menggunakan File Konfigurasi](/id/docs/tasks/manage-kubernetes-objects/imperative-config/) </del> <ins> - [Pengelolaan Objek Kubernetes secara Imperatif Menggunakan Berkas Konfigurasi](/id/docs/tasks/manage-kubernetes-objects/imperative-config/) </ins> - [Rujukan Perintah Kubectl](/docs/reference/generated/kubectl/kubectl-commands/) - [Rujukan API Kubernetes](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/)

This issue is intended for contributor workshop as part of Cloud Native Day Indonesia on 7th Nov 2020. Please don't take it if you are not part of the workshop. There are several old translated pages that contain the english glossary "file", supposed to use Indonesian "berkas" as per KBBI. Please claim the task to fix them by giving comments on this Github issue. /language id Tasks to fix "file" -"berkas": [x] docs/tasks/manage-kubernetes-objects/imperative-[x] docs/tasks/manage-kubernetes-objects/declarative-[ ] docs/tasks/manage-kubernetes-objects/imperative-[ ] docs/tasks/configure-pod-container/configure-pod-[ ] docs/tasks/administer-cluster/sysctl-[ ] [x] [ ] docs/concepts/storage/storage-[ ] docs/concepts/services-networking/connect-applications-[ ] docs/concepts/services-[x] [x] docs/concepts/cluster-
/triage accepted
/assign
I'm taking this page docs/tasks/manage-kubernetes-objects/imperative-
/reopen
Reopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
i'm taking this page docs/tasks/manage-kubernetes-objects/declarative-
may i change this file:
thanks feel free to raise the PR and link this issue
/reopen
Reopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
I take this page :
please let me change another part. I will try to change this file
sure just mention this issue number when you raise the pull request /reopen
Reopened this issue. <detailsIn response to : please let me change another part sure just mention this issue number when you raise the pull request Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with . Send feedback to sig-contributor-experience at . /lifecycle stale
Stale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-contributor-experience at . /lifecycle rotten
Rotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . Send feedback to sig-contributor-experience at . /close
Closing this issue. <detailsIn response to : Rotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . /close Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details


Question: Traffic from the external load balancer is directed at the backend Pods. The cloud provider decides how it is load balanced. <del> Some cloud providers allow you to specify the `loadBalancerIP`. In those cases, the load-balancer is created with the user-specified `loadBalancerIP`. If the `loadBalancerIP` field is not specified, the loadBalancer is set up with an ephemeral IP address. If you specify a `loadBalancerIP` but your cloud provider does not support the feature, the `loadbalancerIP` field that you set is ignored. </del> To implement a Service of `type: LoadBalancer`, Kubernetes typically starts off by making the changes that are equivalent to you requesting a Service of `type: NodePort`. The cloud-controller-manager component then configures the external load balancer to

This is a Bug Report Problem: As per , the has been deprecated since 1.24 but the docs does not mention about the deprecation - Proposed Solution: should mention the deprecation at least. Page to Update:
/triage accepted
Hi , the triage has been accepted and if you want to contribute the change you can assign it to yourself . If not, please let us know here, I'll be happy to add this
Thank you. Please go ahead
Great . Thanks /assign
/sig apps /sig network /sig docs
Continuing the discussion for change: One way we can apply this change is by adding a note: But should we give an example of the annotations ?
Hi , Raised a PR for the Note:


Question: * kms plugin version: `v1beta1` <del> In response to procedure call Version, a compatible KMS plugin should return v1beta1 as VersionResponse.version </del> <ins> In response to procedure call Version, a compatible KMS plugin should return v1beta1 as VersionResponse.version. </ins> * message version: `v1beta1` <del> All messages from KMS provider have the version field set to current version v1beta1 </del> <ins> All messages from KMS provider have the version field set to current version v1beta1. </ins> * protocol: UNIX domain socket (`unix`) <del> The gRPC server should listen at UNIX domain socket </del> <ins> The gRPC server should listen at UNIX domain socket. </ins> ### Integrating a KMS plugin with the remote KMS The KMS plugin can communicate with the remote KMS using any protocol supported by the KMS. All configuration data, including authentication credentials the KMS plugin uses to communicate with the remote KMS, are stored and managed by the KMS plugin independently. The KMS plugin can encode the ciphertext with additional metadata that may be required before sending it to the KMS for decryption.

This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: There are indentation errors in the yaml files of EncryptionConfiguration. For example in the following yaml, lines after "- secrets" should indent two to the right. ! Proposed Solution: Correct the indentation errors. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
Is it right to have in the fixed page?
I checked the preview page, and it's still wrong. I've close my PR.
It should looks like this or "secrets" is the subcontent of the second "resources", and "providers" is with the same level of the second "resources". Although I modified the markdown, the rendered webpage is still wrong.
/priority backlog /language en /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 : /priority backlog /language en /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
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 /assign


Question: ``` As you can see from the results of the command, the cron job has not scheduled or run any jobs yet. <del> Watch for the job to be created in around one minute: </del> <ins> {{< glossary_tooltip text="Watch" term_id="watch" >}} for the job to be created in around one minute: </ins> ```shell kubectl get jobs --watch

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 Update the to include an explanation of “watch”. Why is this needed The watch verb (and actually watchcollection as well) is K8s-specific jargon. We should help readers understand it. Comments Extra credit for also using the new term in existing pages, using a . /kind feature /wg api-expression
/assign
/priority backlog /triage accepted
Hi PR: for this issue. PTAL
I'm happy for any reviewer (for English) to take a look there.


Question: Being vulnerable does not necessarily mean that your service will be exploited. Though your services are vulnerable in some ways unknown to you, offenders still need to identify these vulnerabilities and then exploit them. If offenders fail to exploit your service vulnerabilities, you win! In other words, having a vulnerability that can’t be exploited, represents a risk that can’t be realized. <del> {{< figure src="Example.png" alt="Image of an example of offender gaining foothold in a service" class="diagram-large" caption="Figure 1. An Offender gaining foothold in a vulnerable service" >}} </del> <ins> {{< figure src="security_behavior_figure_1.svg" alt="Image of an example of offender gaining foothold in a service" class="diagram-large" caption="Figure 1. An Offender gaining foothold in a vulnerable service" >}} </ins> The above diagram shows an example in which the offender does not yet have a foothold in the service; that is, it is assumed that your service does not run code controlled by the offender on day 1. In our example the service has vulnerabilities in the API exposed to clients. To gain an initial foothold the offender uses a malicious client to try and exploit one of the service API vulnerabilities. The malicious client sends an exploit that triggers some unplanned behavior of the service.

This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: The image files in need to be converted to an SVG. Currently, they are PNG. The originals are PPT files that can be found at Earlier attempts to convert them to SVG resulted in poor-quality images. Proposed Solution: If anyone has the tools and expertise to convert the PNG/PPT to high-quality SVG that will look the same as the PNGs, we welcome the help. Page to Update: <!--Optional Information (remove the comment tags around the information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/assign If anyone gets to this first: great!
hey! looking to contribute to this project !..can I?
/triage accepted
I've made progress on this and hope to send in a PR later this week.


Question: {{< note >}} Kubeadm uses the same `KubeletConfiguration` for all nodes in the cluster. <del> The `KubeletConfiguration` is stored in a [ConfigMap](docs/concepts/configuration/configmap) </del> <ins> The `KubeletConfiguration` is stored in a [ConfigMap](/docs/concepts/configuration/configmap) </ins> object under the `kube-system` namespace. Executing the sub commands `init`, `join` and `upgrade` would result in kubeadm

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: In there is a table broken with GitHub Markdown renderer. ! BTW, the table is not broken with Hugo Markdown renderer. ! Proposed Solution: Page to Update: No Page on to Update. Just a Markdown file on GitHub to update. <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/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
We support viewing the rendered documentation via I don't think this issue is valid.
/priority awaiting-more-evidence /langauge en
Thank for your comment. I will describe a bit more about this issue I opened. [As-is] Yes, although the second row of the Markdown code has 4 columns and other rows have 3 columns, this table is rendered alright by Hugo Markdown renderer. This is a issue about improving consistency of the number of columns in the Markdown code, regardless of the type of Markdown renderer. [To-be]

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: In , the link is broken. Proposed Solution: In Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/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
already logged here: /close /sig cluster-lifecycle
Closing this issue. <detailsIn response to : already logged here: /sig cluster-lifecycle 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: ShutdownGracePeriod specifies the total duration that the node should delay the shutdown and total grace period for pod termination during a node shutdown.  Default: "30s"	   Default: "0s"

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: Visiting provides inaccurate default values for shutdownGracePeriod (30s rather than 0s) and shutdownGracePeriodCriticalPods (10s rather than 0s). Proposed Solution: Correct the documentation to match the actual default values. 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
I would like to take up this ticket.


Question: * endpoints * nodes * pods <del> * secrets, configmaps, persistent volume claims and persistent volumes related to pods bound to the kubelet's node </del> <ins> * secrets, configmaps, persistent volume claims and persistent volumes related to pods bound to the kubelet's node </ins> Write operations: <del> * nodes and node status (enable the `NodeRestriction` admission plugin to limit a kubelet to modify its own node) * pods and pod status (enable the `NodeRestriction` admission plugin to limit a kubelet to modify pods bound to itself) </del> <ins> * nodes and node status (enable the `NodeRestriction` admission plugin to limit a kubelet to modify its own node) * pods and pod status (enable the `NodeRestriction` admission plugin to limit a kubelet to modify pods bound to itself) </ins> * events Auth-related operations: <del> * read/write access to the [CertificateSigningRequests API](/docs/reference/access-authn-authz/certificate-signing-requests/) for TLS bootstrapping * the ability to create TokenReviews and SubjectAccessReviews for delegated authentication/authorization checks </del> <ins> * read/write access to the [CertificateSigningRequests API](/docs/reference/access-authn-authz/certificate-signing-requests/) for TLS bootstrapping * the ability to create TokenReviews and SubjectAccessReviews for delegated authentication/authorization checks </ins> <del> In future releases, the node authorizer may add or remove permissions to ensure kubelets have the minimal set of permissions required to operate correctly. </del> <ins> In future releases, the node authorizer may add or remove permissions to ensure kubelets have the minimal set of permissions required to operate correctly. </ins> <del> In order to be authorized by the Node authorizer, kubelets must use a credential that identifies them as being in the `system:nodes` group, with a username of `system:node:<nodeName>`. </del> <ins> In order to be authorized by the Node authorizer, kubelets must use a credential that identifies them as being in the `system:nodes` group, with a username of `system:node:<nodeName>`. </ins> This group and user name format match the identity created for each kubelet as part of [kubelet TLS bootstrapping](/docs/reference/access-authn-authz/kubelet-tls-bootstrapping/). <del> The value of `<nodeName>` **must** match precisely the name of the node as registered by the kubelet. By default, this is the host name as provided by `hostname`, or overridden via the [kubelet option](/docs/reference/command-line-tools-reference/kubelet/) `--hostname-override`. However, when using the `--cloud-provider` kubelet option, the specific hostname may be determined by the cloud provider, ignoring the local `hostname` and the `--hostname-override` option. For specifics about how the kubelet determines the hostname, see the [kubelet options reference](/docs/reference/command-line-tools-reference/kubelet/). </del> <ins> The value of `<nodeName>` **must** match precisely the name of the node as registered by the kubelet. By default, this is the host name as provided by `hostname`, or overridden via the [kubelet option](/docs/reference/command-line-tools-reference/kubelet/) `--hostname-override`. However, when using the `--cloud-provider` kubelet option, the specific hostname may be determined by the cloud provider, ignoring the local `hostname` and the `--hostname-override` option. For specifics about how the kubelet determines the hostname, see the [kubelet options reference](/docs/reference/command-line-tools-reference/kubelet/). </ins> To enable the Node authorizer, start the apiserver with `--authorization-mode=Node`. <del> To limit the API objects kubelets are able to write, enable the [NodeRestriction](/docs/reference/access-authn-authz/admission-controllers#noderestriction) admission plugin by starting the apiserver with `--enable-admission-plugins=...,NodeRestriction,...` </del> <ins> To limit the API objects kubelets are able to write, enable the [NodeRestriction](/docs/reference/access-authn-authz/admission-controllers#noderestriction) admission plugin by starting the apiserver with `--enable-admission-plugins=...,NodeRestriction,...` </ins> ## Migration considerations ### Kubelets outside the `system:nodes` group <del> Kubelets outside the `system:nodes` group would not be authorized by the `Node` authorization mode, and would need to continue to be authorized via whatever mechanism currently authorizes them. </del> <ins> Kubelets outside the `system:nodes` group would not be authorized by the `Node` authorization mode, and would need to continue to be authorized via whatever mechanism currently authorizes them. </ins> The node admission plugin would not restrict requests from these kubelets. ### Kubelets with undifferentiated usernames

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 <!-- Describe as precisely as possible how this feature/enhancement should work from the user perspective. What should be changed, etc. --2 sections below may include too old content, mentioning v1.6 ~ v1.8. They should be removed or updated. Upgrades from previous versions using RBAC RBAC Node Permissions Why is this needed Too old content may not be needed or should not be included in the latest document. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/language en /kind cleanup
/triage accepted /sig auth I think
/assign
Rather than remove those sections, let's update them to clarify why they remain valid.
/kind documentation
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
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]:
/remove-lifecycle rotten
/remove-kind feature /kind bug /priority backlog
Those labels are not set on the issue: <detailsIn response to : /remove-kind feature /kind bug /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
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]:
/remove-lifecycle rotten
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]:
/lifecycle frozen The update needed is to delete the page content from onwards (including that heading) /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 : /lifecycle frozen 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
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


Question:
---  title: Hello Minikube   title: Bienvenue sur Minikube  content_type: tutorial weight: 5  description: Tutoriel Minikube menu: main: title: "Démarrer" weight: 10 post: >
Prêt à mettre les mains dans le cambouis ? Créez un cluster Kubernetes simple qui exécute "Hello World" avec Node.js.
>.  card: name: tutorials weight: 10

Bonjour, Petit problème de CORS sur cette page: Je suis bien sur un ordinateur et j'ai ceci: !
/retitle [fr] Inactive and deprecated interactive tutorial in "Learn Kubernetes Basics" page /language fr
Katacoda environment for the Kubernetes tutorial has been shut down. Refer the announcement . We have an umbrella issue raised to remove tutorials that rely on Katacoda for all localized documents.
/area localization /kind bug
Does it mean I can suggest a merge request for French?
/triage accepted Ce projet est open source : tout le monde peut y contribuer! / This is an open source project, anyone is welcome to contribute!


Question: 1. इस कमांड से नवीनतम रिलीज डाउनलोड करें: ```powershell <del> curl -LO https://dl.k8s.io/release/{{% param "fullversion" %}}/bin/windows/amd64/kubectl-convert.exe </del> <ins> curl -LO https://dl.k8s.io/release/v{{< skew currentPatchVersion >}}/bin/windows/amd64/kubectl-convert.exe </ins> ``` 1. बाइनरी को मान्य करें (वैकल्पिक)

Parent issue: Substitute the outdated shortcode with the new shortcode in the Hindi language documentation. /assign /triage accepted /language hi
PR has been raised to address this issue.


Question: {{< feature-state state="stable" for_k8s_version="v1.25" >}} You should set the `.spec.os.name` field to either `windows` or `linux` to indicate the OS on <del> which you want the pod to run. These two are the only operating systems supported for now by Kubernetes. In future, this list may be expanded. In Kubernetes v{{< skew currentVersion >}}, the value you set for this field has no effect on {{< glossary_tooltip text="scheduling" term_id="kube-scheduler" >}} of the pods. Setting the `.spec.os.name` helps to identify the pod OS authoritatively and is used for validation. The kubelet refuses to run a Pod where you have specified a Pod OS, if this isn't the same as the operating system for the node where that kubelet is running. </del> <ins> which you want the pod to run. These two are the only operating systems supported for now by Kubernetes. In the future, this list may be expanded. In Kubernetes v{{< skew currentVersion >}}, the value of `.spec.os.name` does not affect how the {{< glossary_tooltip text="kube-scheduler" term_id="kube-scheduler" >}} picks a Pod to run a node. In any cluster where there is more than one operating system for running nodes, you should set the [kubernetes.io/os](/docs/reference/labels-annotations-taints/#kubernetes-io-os) label correctly on each node, and define pods with a `nodeSelector` based on the operating system label, the kube-scheduler assigns your pod to a node based on other criteria and may or may not succeed in picking a suitable node placement where the node OS is right for the containers in that Pod. </ins> The [Pod security standards](/docs/concepts/security/pod-security-standards/) also use this <del> field to avoid enforcing policies that aren't relevant to that operating system. </del> <ins> field to avoid enforcing policies that aren't relevant to the operating system. </ins> ### Pods and controllers

While reading the documentation about the OS spec for it states: Pod OS FEATURE STATE: Kubernetes v1.25 [stable] You should set the field to either windows or linux to indicate the OS on which you want the pod to run. These two are the only operating systems supported for now by Kubernetes. In future, this list may be expanded. In Kubernetes v1.26, the value you set for this field has no effect on of the pods. Setting the helps to identify the pod OS authoratitively and is used for validation. The kubelet refuses to run a Pod where you have specified a Pod OS, if this isn't the same as the operating system for the node where that kubelet is running. The also use this field to avoid enforcing policies that aren't relevant to that operating system. The second paragraph mentions 1.26 doesn't take this field into consideration to schedule the pod but later in the same paragraph it states kubelet will take this field in consideration to schedule the pod (assigning the pod to a matching OS node). Am I reading it incorrectly or the paragraph should read "In Kubernetes v1.25, the vaule you set for this field has no effect on scheduling" ?
is correct, but perhaps misleading. How about changing the order round: Kubernetes v1.26 uses the value of to validate Pods (the kubelet checks that the Pod OS matches the operating system that the kubelet is running on). If you create (or try to create a Pod) in a namespace that uses Pod security admission, the control plane also uses the value of to work out what restrictions to verify and / or enforce. In Kubernetes v1.26, the value of does not affect how the picks a Pod to run a node. In any cluster where there is more than one operating system for nodes, you should set the  label correctly on each nodes, and define Pods with a than matches the correct operating system. If you set anddo not specify a based on the operating system label, the scheduler assigns your pod to a node based on other criteria and may or may not succeed in picking a suitable node placement where the node OS is right for the containers in that Pod. ? We could link to a task page that explains how to assign Linux Pods to Linux nodes, and Windows Pods to Windows nodes (if we had such a task page).

/sig node
/language en
Hi by your message I understand that: Kubelet will fail to run a pod with a non matching in the node that is running (as if a Linux pod is assigned to a Windows Node for example) Kube-Scheduler will not take into account to define in which node to run a pod (unless a label is specified) so it would potentially scheduling a Linux pod in a Windows node. Am I getting it right? if so I believe your message is great to be a replacement of the one in the current documentation. Just there is a missing space in this paragraph (getting a bit picky sorry ) If you set not specify a nodeSelector based on the operating system label, the scheduler assigns your pod to a node based on other criteria and may or may not succeed in picking a suitable node placement where the node OS is right for the containers in that Pod.
This could warrant a PR since the fix is clear. /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 could warrant a PR since the fix is clear. /help </details
/triage accepted
/assign
Also see /retitle Pod OS spec description is not clear
/assign


Question: | --- | --- | --- | --- | --- | | [release-managers@kubernetes.io](mailto:release-managers@kubernetes.io) | [#release-management](https://kubernetes.slack.com/messages/CJH2GBF7Y) (channel) / @release-managers (user group) | Public | Public discussion for Release Managers | All Release Managers (including Associates, Build Admins, and SIG Chairs) | | [release-managers-private@kubernetes.io](mailto:release-managers-private@kubernetes.io) | N/A | Private | Private discussion for privileged Release Managers | Release Managers, SIG Release leadership | <del> | [security-release-team@kubernetes.io](mailto:security-release-team@kubernetes.io) | [#security-release-team](https://kubernetes.slack.com/archives/G0162T1RYHG) (channel) / @security-rel-team (user group) | Private | Security release coordination with the Product Security Committee | [security-discuss-private@kubernetes.io](mailto:security-discuss-private@kubernetes.io), [release-managers-private@kubernetes.io](mailto:release-managers-private@kubernetes.io) | </del> <ins> | [security-release-team@kubernetes.io](mailto:security-release-team@kubernetes.io) | [#security-release-team](https://kubernetes.slack.com/archives/G0162T1RYHG) (channel) / @security-rel-team (user group) | Private | Security release coordination with the Security Response Committee | [security-discuss-private@kubernetes.io](mailto:security-discuss-private@kubernetes.io), [release-managers-private@kubernetes.io](mailto:release-managers-private@kubernetes.io) | </ins> ### Security Embargo Policy

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 change We should find the term “product security committee” anywhere within the English-language docs, and replace that term with “security response committee”. We don't need to revise any blog articles. If we feel there are some blog articles where an exception is justified, I'd revise those in a separate PR per article as the review process is different. Why is this needed renamed the product security committee to “Security Response Committee” Comments /language en /sig docs /sig security /help /triage accepted Relevant to
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 : This is a Feature Request <!-- See for guidance on writing an actionable issue description. --We should find the term “product security committee” anywhere within the English-language docs, and replace that term with “security response committee”. We don't need to revise any blog articles. If we feel there are some blog articles where an exception is justified, I'd revise those in a separate PR per article as the review process is different. renamed the product security committee to “Security Response Committee” /language en /sig docs /sig security /help /triage accepted Relevant to 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
/priority backlog
thanks , PR's are incoming org wide for the change.
Hi, I would like to take this up /assign


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

Parent issue: Replace the deprecated shortcode with the shortcode in the Brazilian Portuguese localized docs. /assign /triage accepted /language pt


Question: <ins> --- title: 拡張リソースのリソースビンパッキング content_type: concept weight: 80 --- <!-- overview --> {{< feature-state for_k8s_version="v1.16" state="alpha" >}} kube-schedulerでは、優先度関数`RequestedToCapacityRatioResourceAllocation`を使用した、 拡張リソースを含むリソースのビンパッキングを有効化できます。優先度関数はそれぞれのニーズに応じて、kube-schedulerを微調整するために使用できます。 <!-- body --> ## `RequestedToCapacityRatioResourceAllocation`を使用したビンパッキングの有効化 Kubernetesでは、キャパシティー比率への要求に基づいたNodeのスコアリングをするために、各リソースの重みと共にリソースを指定することができます。これにより、ユーザーは適切なパラメーターを使用することで拡張リソースをビンパックすることができ、大規模クラスターにおける希少なリソースを有効活用できるようになります。優先度関数`RequestedToCapacityRatioResourceAllocation`の動作は`RequestedToCapacityRatioArgs`と呼ばれる設定オプションによって変わります。この引数は`shape`と`resources`パラメーターによって構成されます。`shape`パラメーターは`utilization`と`score`の値に基づいて、最も要求が多い場合か最も要求が少ない場合の関数をチューニングできます。`resources`パラメーターは、スコアリングの際に考慮されるリソース名の`name`と、各リソースの重みを指定する`weight`で構成されます。 以下は、拡張リソース`intel.com/foo`と`intel.com/bar`のビンパッキングに`requestedToCapacityRatioArguments`を設定する例になります。 ```yaml apiVersion: kubescheduler.config.k8s.io/v1beta1 kind: KubeSchedulerConfiguration profiles: # ... pluginConfig: - name: RequestedToCapacityRatio args: shape: - utilization: 0 score: 10 - utilization: 100 score: 0 resources: - name: intel.com/foo weight: 3 - name: intel.com/bar weight: 5 ``` スケジューラーには、kube-schedulerフラグ`--config=/path/to/config/file`を使用して`KubeSchedulerConfiguration`のファイルを指定することで渡すことができます。 **この機能はデフォルトで無効化されています** ### 優先度関数のチューニング `shape`は`RequestedToCapacityRatioPriority`関数の動作を指定するために使用されます。 ```yaml shape: - utilization: 0 score: 0 - utilization: 100 score: 10 ``` 上記の引数は、`utilization`が0%の場合は0、`utilization`が100%の場合は10という`score`をNodeに与え、ビンパッキングの動作を有効にしています。最小要求を有効にするには、次のようにスコアを反転させる必要があります。 ```yaml shape: - utilization: 0 score: 10 - utilization: 100 score: 0 ``` `resources`はオプションパラメーターで、デフォルトでは以下の通りです。 ``` yaml resources: - name: cpu weight: 1 - name: memory weight: 1 ``` 以下のように拡張リソースの追加に利用できます。 ```yaml resources: - name: intel.com/foo weight: 5 - name: cpu weight: 3 - name: memory weight: 1 ``` `weight`はオプションパラメーターで、指定されてない場合1が設定されます。また、マイナスの値は設定できません。 ### キャパシティ割り当てのためのNodeスコアリング このセクションは、本機能の内部詳細について理解したい方を対象としています。以下は、与えられた値に対してNodeのスコアがどのように計算されるかの例です。 要求されたリソース: ``` intel.com/foo : 2 memory: 256MB cpu: 2 ``` リソースの重み: ``` intel.com/foo : 5 memory: 1 cpu: 3 ``` `shape`の値 {{0, 0}, {100, 10}} Node1のスペック: ``` Available: intel.com/foo: 4 memory: 1 GB cpu: 8 Used: intel.com/foo: 1 memory: 256MB cpu: 1 ``` Nodeのスコア: ``` intel.com/foo  = resourceScoringFunction((2+1),4) = (100 - ((4-3)*100/4) = (100 - 25) = 75                       # requested + used = 75% * available = rawScoringFunction(75) = 7                        # floor(75/10) memory         = resourceScoringFunction((256+256),1024) = (100 -((1024-512)*100/1024)) = 50                       # requested + used = 50% * available = rawScoringFunction(50) = 5                        # floor(50/10) cpu            = resourceScoringFunction((2+1),8) = (100 -((8-3)*100/8)) = 37.5                     # requested + used = 37.5% * available = rawScoringFunction(37.5) = 3                        # floor(37.5/10) NodeScore   =  (7 * 5) + (5 * 1) + (3 * 3) / (5 + 1 + 3) =  5 ``` Node2のスペック: ``` Available: intel.com/foo: 8 memory: 1GB cpu: 8 Used: intel.com/foo: 2 memory: 512MB cpu: 6 ``` Nodeのスコア: ``` intel.com/foo  = resourceScoringFunction((2+2),8) =  (100 - ((8-4)*100/8) =  (100 - 50) =  50 =  rawScoringFunction(50) = 5 memory         = resourceScoringFunction((256+512),1024) = (100 -((1024-768)*100/1024)) = 75 = rawScoringFunction(75) = 7 cpu            = resourceScoringFunction((2+6),8) = (100 -((8-8)*100/8)) = 100 = rawScoringFunction(100) = 10 NodeScore   =  (5 * 5) + (7 * 1) + (10 * 3) / (5 + 1 + 3) =  7 ``` ## {{% heading "whatsnext" %}} - [スケジューリングフレームワーク](/ja/docs/concepts/scheduling-eviction/scheduling-framework/)について更に読む - [スケジューラーの設定](/docs/reference/scheduling/config/)について更に読む </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 <!-- Describe as precisely as possible how this feature/enhancement should work from the user perspective. What should be changed, etc. --Translate into Japanese. Why is this needed This page has not been translated. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/language ja /assign
/triage accepted


Question: All of the following are responsibilities of whoever sets up and manages the cluster: 1. Creating the CA key and certificate <del> 2. Distributing the CA certificate to the master nodes, where kube-apiserver is running </del> <ins> 2. Distributing the CA certificate to the control plane nodes, where kube-apiserver is running </ins> 3. Creating a key and certificate for each kubelet; strongly recommended to have a unique one, with a unique CN, for each kubelet 4. Signing the kubelet certificate using the CA key 5. Distributing the kubelet key and signed certificate to the specific node on which the kubelet is running

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: uses the outdated term “master” and “master node”. Proposed Solution: Replace references to the control plane that use the term “master” with the current term: “control plane”. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /language en /kind cleanup /wg naming
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/retitle “Kubelet TLS Bootstrapping” uses outdated wording
I would like to take up this issue
/assign