{"id":53857,"date":"2019-12-12T00:00:00","date_gmt":"2019-12-11T21:00:00","guid":{"rendered":"https:\/\/prohoster.info\/blog\/blog_prohoster\/kubernetes-1-17-kak-obnovitsya-i-ne-potratit-ves-error-budget"},"modified":"2020-02-18T14:01:47","modified_gmt":"2020-02-18T11:01:47","slug":"kubernetes-1-17-kak-obnovitsya-i-ne-potratit-ves-error-budget","status":"publish","type":"post","link":"https:\/\/prohoster.info\/hu\/blog\/administrirovanie\/kubernetes-1-17-kak-obnovitsya-i-ne-potratit-ves-error-budget","title":{"rendered":"Kubernetes 1.17 \u2014 hogyan friss\u00edts\u00fck, an\u00e9lk\u00fcl hogy elfogyjon az error budget","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\"Kubernetes
\n
\nDecember 9 saw the release of the new version of Kubernetes \u2014 1.17. Its motto is \"Stability\", numerous features have achieved GA status, and some deprecated features have been removed\u2026<\/p>\n

And, as always, our favorite section Action Required of the file CHANGELOG-1.17.md<\/a><\/noindex> requires attention.<\/p>\n

Let's work with our hands\u2026
\n<\/a><\/noindex><\/p>\n

Attention, Storage!<\/h3>\n

\nIn version 1.17, updating kubelet on the fly is not supported, as the path to block volumes has changed. Before updating the node, you need to evict all pods from it using the command kubectl drain<\/code>.<\/p>\n

Z\u00e1szl\u00f3k \u00e9s kapuk\u2026<\/h4>\n

\nA changelogban \u00e1ltal\u00e1ban azt \u00edrj\u00e1k, hogy elt\u00e1vol\u00edtottak vagy hozz\u00e1adtak egy adott flagot vagy feature gate-et, de valami\u00e9rt soha nem eml\u00edtik az alkalmaz\u00e1st, amelyn\u00e9l ez a v\u00e1ltoz\u00e1s t\u00f6rt\u00e9nt\u2026:<\/p>\n