Question:
{{- $single := .Get "single" | default "false" -}}  {{- $vendor_message := .Get "vendor" | default "false" -}}
 {{- if not (eq $single "true" ) -}} {{ T "note" | safeHTML }}  {{ T "thirdparty_message" | safeHTML }}   {{- if (eq $vendor_message "true" ) -}} {{ T "thirdparty_message_vendor" | safeHTML }} {{- else -}} {{ T "thirdparty_message" | safeHTML }} {{- end -}}  {{- else -}} {{ T "thirdparty_message_single_item" | safeHTML }} {{- end -}}

This is a Refactor request <!-- 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 overview page at is a bit out of date: no reference to I'm not convinced that the “Four Cs of cloud native security” model is useful for readers to learn Does not align with other CNCF documents, such as Proposed Solution: Either: remove outright migrate content from into several destinations (keep this brief but on-point) …and then redirect to Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /sig docs /sig security /language en
If we keep the link to then we should update it to be as this is the English docs.
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]:
/remove-lifecycle stale /triage accepted
Also see
/assign
I'd appreciate a (fresh) review on .


Question: (ex: `ca.crt`, `ca.key`, `front-proxy-ca.crt`, and `front-proxy-ca.key`) to all your control plane nodes in the Kubernetes certificates directory. <del> 1. Update *Kubernetes controller manager's* `--root-ca-file` to include both old and new CA and restart controller manager. </del> <ins> 1. Update {{< glossary_tooltip text="kube-controller-manager" term_id="kube-controller-manager" >}}'s `--root-ca-file` to include both old and new CA. Then restart the component. </ins> Any service account created after this point will get secrets that include both old and new CAs. {{< note >}} <del> Remove the flag `--client-ca-file` from the *Kubernetes controller manager* configuration. You can also replace the existing client CA file or change this configuration item to reference a new, updated CA. [Issue 1350](https://github.com/kubernetes/kubeadm/issues/1350) tracks an issue with *Kubernetes controller manager* being unable to accept a CA bundle. </del> <ins> The files specified by the kube-controller-manager flags `--client-ca-file` and `--cluster-signing-cert-file` cannot be CA bundles. If these flags and `--root-ca-file` point to the same `ca.crt` file which is now a bundle (includes both old and new CA) you will face an error. To workaround this problem you can copy the new CA to a separate file and make the flags `--client-ca-file` and `--cluster-signing-cert-file` point to the copy. Once `ca.crt` is no longer a bundle you can restore the problem flags to point to `ca.crt` and delete the copy. </ins> {{< /note >}} 1. Update all service account tokens to include both old and new CA certificates.

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 is a remark that mixes up two issues: is not about , rather it is about . even actually relevant to kube-controller-manager? Ayodele Abejide and I can not see any relevant for it (). 1350 looks like a show-stopper for this recipe. Proposed Solution: Fix the recipe. Fix issue 1350. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/sig auth /language en
/kind bug (seems valid to me)
Note: Remove the flag --client-ca-file from the Kubernetes controller manager configuration. You can also replace the existing client CA file or change this configuration item to reference a new, updated CA. Issue 1350 tracks an issue with Kubernetes controller manager being unable to accept a CA bundle. i think the problem that --client-ca-file and --cluster-signing-cert-file flags share is that the KCM does not allow CA bundles for both of them. this also implies complications around this guide. the kubeadm ticket is noisy and i don't think it should be linked from this page. note that the step above mentions: Update Kubernetes controller manager's --root-ca-file to include both old and new CA and restart controller manager. at that point if the same file is a bundle the KCM would just error out because of --client-ca-file, thus the recommendation about removal or making it point to a separate CA. used for client certificate authentication to allow clients to validate the signature of the serving certificate. the KCM can still be served over HTTPs. i guess not if the flag is removed from from the KCM, until the old CA is removed from the bundle at which point the flag can be re-. i think there are wider problems here and we should have an issue in k/k tagged with sig/auth that tracks progress on the KCM supporting bundles.

i've seen mentions around this being worked on here: the note in this document needs clarification: it should link to the k/k issue, if one day the KCM --client-ca-file supports bundles it should explain why the flag is being removed and what are the consequences of doing that (e.g. MITM?). should the flag removal be temporary until the bundle no longer has the old CA? cc
In my opinion, the flag is still needed, when I tested the recipe there were 2 problems at the start, one from and another from , that when I found to be problematic, the point that later only got caught when I removed chain from . That's why I included this in the recipe, that we should either remove it or replace it with the new CA, whichever fits the need cluster to cluster basis. It doesn't makes it show stopper but, yes, I agree that the page needs a bit reword in the paragraph to make it less confusing for people following it.
PS: Just in case someone wants to re-validate, the error I was getting with with old+new CA certs was similar to "certificate signed by unknown authority" and stopped when I replaced it with only new CA. So it was more like the first bundle in the chain was accepted but the newer one did not.
/priority awaiting-more-evidence Please feel free to /priority some-other-value and /triage accepted if this is confirmed valid.
would you like send a PR to amend the paragraph? EDIT: NVM i've sent the PR here, PTAL:
(sent the PR) /remove-priority awaiting-more-evidence /priority backlog
/triage accepted


Question: You can [download Kubernetes](/releases/download/) to deploy a Kubernetes cluster on a local machine, into the cloud, or for your own datacenter. <del> Several [Kubernetes components](/docs/concepts/overview/components/) such as `kube-apiserver` or `kube-proxy` can also be </del> <ins> Several [Kubernetes components](/docs/concepts/overview/components/) such as {{< glossary_tooltip text="kube-apiserver" term_id="kube-apiserver" >}} or {{< glossary_tooltip text="kube-proxy" term_id="kube-proxy" >}} can also be </ins> deployed as [container images](/releases/download/#container-images) within the cluster. It is **recommended** to run Kubernetes components as container images wherever

What would you like to be Under page, provide hyperlink for Why is this needed Adding the hyperlink will helps the readers to know about kube-apiserver. Comments /sig docs /language en /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
/assign
/remove-good-first-issue
/sig docs
I'd use a .
shall i proceed with glossary tooltip?


Question:
 --- title: kube-scheduler Policy Configuration (v1) content_type: tool-reference package: kubescheduler.config.k8s.io/v1 auto_generated: true --- ## Resource Types - [Policy](#kubescheduler-config-k8s-io-v1-Policy) ## `Policy`     {#kubescheduler-config-k8s-io-v1-Policy} Policy describes a struct for a policy resource used in api.

Field	Description

apiVersion
string	kubescheduler.config.k8s.io/v1

kind
string	Policy

predicates [Required]
 []PredicatePolicy 	  Holds the information to configure the fit predicate functions

priorities [Required]
 []PriorityPolicy 	  Holds the information to configure the priority functions

extenders [Required]
 []LegacyExtender 	  Holds the information to communicate with the extender(s)

hardPodAffinitySymmetricWeight [Required]
 int32 	  RequiredDuringScheduling affinity is not symmetric, but there is an implicit PreferredDuringScheduling affinity rule corresponding to every RequiredDuringScheduling affinity rule. HardPodAffinitySymmetricWeight represents the weight of implicit PreferredDuringScheduling affinity rule, in the range 1-100.

alwaysCheckAllPredicates [Required]
 bool 	  When AlwaysCheckAllPredicates is set to true, scheduler checks all the configured predicates even after one or more of them fails. When the flag is set to false, scheduler skips checking the rest of the predicates after it finds one predicate that failed.

 ## `ExtenderManagedResource`     {#kubescheduler-config-k8s-io-v1-ExtenderManagedResource} **Appears in:** - [Extender](#kubescheduler-config-k8s-io-v1beta1-Extender) - [LegacyExtender](#kubescheduler-config-k8s-io-v1-LegacyExtender) ExtenderManagedResource describes the arguments of extended resources managed by an extender.

Field	Description

name [Required]
 string 	  Name is the extended resource name.

ignoredByScheduler [Required]
 bool 	  IgnoredByScheduler indicates whether kube-scheduler should ignore this resource when applying predicates.

 ## `ExtenderTLSConfig`     {#kubescheduler-config-k8s-io-v1-ExtenderTLSConfig} **Appears in:** - [Extender](#kubescheduler-config-k8s-io-v1beta1-Extender) - [LegacyExtender](#kubescheduler-config-k8s-io-v1-LegacyExtender) ExtenderTLSConfig contains settings to enable TLS with extender

Field	Description

insecure [Required]
 bool 	  Server should be accessed without verifying the TLS certificate. For testing only.

serverName [Required]
 string 	  ServerName is passed to the server for SNI and is used in the client to check server certificates against. If ServerName is empty, the hostname used to contact the server is used.

certFile [Required]
 string 	  Server requires TLS client certificate authentication

keyFile [Required]
 string 	  Server requires TLS client certificate authentication

caFile [Required]
 string 	  Trusted root certificates for server

certData [Required]
 []byte 	  CertData holds PEM-encoded bytes (typically read from a client certificate file). CertData takes precedence over CertFile

keyData [Required]
 []byte 	  KeyData holds PEM-encoded bytes (typically read from a client certificate key file). KeyData takes precedence over KeyFile

caData [Required]
 []byte 	  CAData holds PEM-encoded bytes (typically read from a root certificates bundle). CAData takes precedence over CAFile

 ## `LabelPreference`     {#kubescheduler-config-k8s-io-v1-LabelPreference} **Appears in:** - [PriorityArgument](#kubescheduler-config-k8s-io-v1-PriorityArgument) LabelPreference holds the parameters that are used to configure the corresponding priority function

Field	Description

label [Required]
 string 	  Used to identify node "groups"

presence [Required]
 bool 	  This is a boolean flag If true, higher priority is given to nodes that have the label If false, higher priority is given to nodes that do not have the label

 ## `LabelsPresence`     {#kubescheduler-config-k8s-io-v1-LabelsPresence} **Appears in:** - [PredicateArgument](#kubescheduler-config-k8s-io-v1-PredicateArgument) LabelsPresence holds the parameters that are used to configure the corresponding predicate in scheduler policy configuration.

Field	Description

labels [Required]
 []string 	  The list of labels that identify node "groups" All of the labels should be either present (or absent) for the node to be considered a fit for hosting the pod

presence [Required]
 bool 	  The boolean flag that indicates whether the labels should be present or absent from the node

 ## `LegacyExtender`     {#kubescheduler-config-k8s-io-v1-LegacyExtender} **Appears in:** - [Policy](#kubescheduler-config-k8s-io-v1-Policy) LegacyExtender holds the parameters used to communicate with the extender. If a verb is unspecified/empty, it is assumed that the extender chose not to provide that extension.

Field	Description

urlPrefix [Required]
 string 	  URLPrefix at which the extender is available

filterVerb [Required]
 string 	  Verb for the filter call, empty if not supported. This verb is appended to the URLPrefix when issuing the filter call to extender.

preemptVerb [Required]
 string 	  Verb for the preempt call, empty if not supported. This verb is appended to the URLPrefix when issuing the preempt call to extender.

prioritizeVerb [Required]
 string 	  Verb for the prioritize call, empty if not supported. This verb is appended to the URLPrefix when issuing the prioritize call to extender.

weight [Required]
 int64 	  The numeric multiplier for the node scores that the prioritize call generates. The weight should be a positive integer

bindVerb [Required]
 string 	  Verb for the bind call, empty if not supported. This verb is appended to the URLPrefix when issuing the bind call to extender. If this method is implemented by the extender, it is the extender's responsibility to bind the pod to apiserver. Only one extender can implement this function.

enableHttps [Required]
 bool 	  EnableHTTPS specifies whether https should be used to communicate with the extender

tlsConfig [Required]
 ExtenderTLSConfig 	  TLSConfig specifies the transport layer security config

httpTimeout [Required]
 time.Duration 	  HTTPTimeout specifies the timeout duration for a call to the extender. Filter timeout fails the scheduling of the pod. Prioritize timeout is ignored, k8s/other extenders priorities are used to select the node.

nodeCacheCapable [Required]
 bool 	  NodeCacheCapable specifies that the extender is capable of caching node information, so the scheduler should only send minimal information about the eligible nodes assuming that the extender already cached full details of all nodes in the cluster

managedResources
 []ExtenderManagedResource 	  ManagedResources is a list of extended resources that are managed by this extender. - A pod will be sent to the extender on the Filter, Prioritize and Bind (if the extender is the binder) phases iff the pod requests at least one of the extended resources in this list. If empty or unspecified, all pods will be sent to this extender. - If IgnoredByScheduler is set to true for a resource, kube-scheduler will skip checking the resource in predicates.

ignorable [Required]
 bool 	  Ignorable specifies if the extender is ignorable, i.e. scheduling should not fail when the extender returns an error or is not reachable.

 ## `PredicateArgument`     {#kubescheduler-config-k8s-io-v1-PredicateArgument} **Appears in:** - [PredicatePolicy](#kubescheduler-config-k8s-io-v1-PredicatePolicy) PredicateArgument represents the arguments to configure predicate functions in scheduler policy configuration. Only one of its members may be specified

Field	Description

serviceAffinity [Required]
 ServiceAffinity 	  The predicate that provides affinity for pods belonging to a service It uses a label to identify nodes that belong to the same "group"

labelsPresence [Required]
 LabelsPresence 	  The predicate that checks whether a particular node has a certain label defined or not, regardless of value

 ## `PredicatePolicy`     {#kubescheduler-config-k8s-io-v1-PredicatePolicy} **Appears in:** - [Policy](#kubescheduler-config-k8s-io-v1-Policy) PredicatePolicy describes a struct of a predicate policy.

Field	Description

name [Required]
 string 	  Identifier of the predicate policy For a custom predicate, the name can be user-defined For the Kubernetes provided predicates, the name is the identifier of the pre-defined predicate

argument [Required]
 PredicateArgument 	  Holds the parameters to configure the given predicate

 ## `PriorityArgument`     {#kubescheduler-config-k8s-io-v1-PriorityArgument} **Appears in:** - [PriorityPolicy](#kubescheduler-config-k8s-io-v1-PriorityPolicy) PriorityArgument represents the arguments to configure priority functions in scheduler policy configuration. Only one of its members may be specified

Field	Description

serviceAntiAffinity [Required]
 ServiceAntiAffinity 	  The priority function that ensures a good spread (anti-affinity) for pods belonging to a service It uses a label to identify nodes that belong to the same "group"

labelPreference [Required]
 LabelPreference 	  The priority function that checks whether a particular node has a certain label defined or not, regardless of value

requestedToCapacityRatioArguments [Required]
 RequestedToCapacityRatioArguments 	  The RequestedToCapacityRatio priority function is parametrized with function shape.

 ## `PriorityPolicy`     {#kubescheduler-config-k8s-io-v1-PriorityPolicy} **Appears in:** - [Policy](#kubescheduler-config-k8s-io-v1-Policy) PriorityPolicy describes a struct of a priority policy.

Field	Description

name [Required]
 string 	  Identifier of the priority policy For a custom priority, the name can be user-defined For the Kubernetes provided priority functions, the name is the identifier of the pre-defined priority function

weight [Required]
 int64 	  The numeric multiplier for the node scores that the priority function generates The weight should be non-zero and can be a positive or a negative integer

argument [Required]
 PriorityArgument 	  Holds the parameters to configure the given priority function

 ## `RequestedToCapacityRatioArguments`     {#kubescheduler-config-k8s-io-v1-RequestedToCapacityRatioArguments} **Appears in:** - [PriorityArgument](#kubescheduler-config-k8s-io-v1-PriorityArgument) RequestedToCapacityRatioArguments holds arguments specific to RequestedToCapacityRatio priority function.

Field	Description

shape [Required]
 []UtilizationShapePoint 	  Array of point defining priority function shape.

resources [Required]
 []ResourceSpec 	  No description provided.

 ## `ResourceSpec`     {#kubescheduler-config-k8s-io-v1-ResourceSpec} **Appears in:** - [RequestedToCapacityRatioArguments](#kubescheduler-config-k8s-io-v1-RequestedToCapacityRatioArguments) ResourceSpec represents single resource and weight for bin packing of priority RequestedToCapacityRatioArguments.

Field	Description

name [Required]
 string 	  Name of the resource to be managed by RequestedToCapacityRatio function.

weight [Required]
 int64 	  Weight of the resource.

 ## `ServiceAffinity`     {#kubescheduler-config-k8s-io-v1-ServiceAffinity} **Appears in:** - [PredicateArgument](#kubescheduler-config-k8s-io-v1-PredicateArgument) ServiceAffinity holds the parameters that are used to configure the corresponding predicate in scheduler policy configuration.

Field	Description

labels [Required]
 []string 	  The list of labels that identify node "groups" All of the labels should match for the node to be considered a fit for hosting the pod

 ## `ServiceAntiAffinity`     {#kubescheduler-config-k8s-io-v1-ServiceAntiAffinity} **Appears in:** - [PriorityArgument](#kubescheduler-config-k8s-io-v1-PriorityArgument) ServiceAntiAffinity holds the parameters that are used to configure the corresponding priority function

Field	Description

label [Required]
 string 	  Used to identify node "groups"

 ## `UtilizationShapePoint`     {#kubescheduler-config-k8s-io-v1-UtilizationShapePoint} **Appears in:** - [RequestedToCapacityRatioArguments](#kubescheduler-config-k8s-io-v1-RequestedToCapacityRatioArguments) UtilizationShapePoint represents single point of priority function shape.

Field	Description

utilization [Required]
 int32 	  Utilization (x axis). Valid values are 0 to 100. Fully utilized node maps to 100.

score [Required]
 int32 	  Score assigned to given utilization (y axis). Valid values are 0 to 10.

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 scheduler policy API was completely removed in 1.23. Proposed Solution: Revise concepts/configuration/manage-resources- to remove references to the scheduler policy API; Revise or even remove which is meaningless; Remove the kube-scheduler-policy- file from config API. Page to Update: See above. <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--Related:
/sig scheduling /language en
/triage accepted


Question: baseURL = "https://kubernetes.io" title = "Kubernetes" # Hugo allows theme composition (and inheritance). The precedence is from left to right. theme = ["docsy"] # Language settings contentDir = "content/en" defaultContentLanguage = "en" defaultContentLanguageInSubdir = false enableRobotsTXT = true disableBrowserError = true disableKinds = ["taxonomy", "taxonomyTerm"] ignoreFiles = [ "(?:^|/)OWNERS$", "README[-]+[a-z]*.md", "^node_modules$", "content/en/docs/doc-contributor-tools" ] timeout = "180s" # Highlighting config. pygmentsCodeFences = true pygmentsUseClasses = false # Use the new Chroma Go highlighter in Hugo. pygmentsUseClassic = false #pygmentsOptions = "linenos=table" # See https://help.farbox.com/pygments.html pygmentsStyle = "emacs" # Enable Git variables like commit, lastmod enableGitInfo = true # Norwegian ("no") is sometimes but not currently used for testing. disableLanguages = ["no"] [caches] [caches.assets] dir = ":cacheDir/_gen" maxAge = -1 [caches.getcsv] dir = ":cacheDir/:project" maxAge = "60s" [caches.getjson] dir = ":cacheDir/:project" maxAge = "60s" [caches.images] dir = ":cacheDir/_images" maxAge = -1 [caches.modules] dir = ":cacheDir/modules" maxAge = -1 [markup] [markup.goldmark] [markup.goldmark.extensions] definitionList = true table = true typographer = false [markup.goldmark.parser] attribute = true autoHeadingID = true autoHeadingIDType = "blackfriday" [markup.goldmark.renderer] unsafe = true [markup.highlight] codeFences = true guessSyntax = false hl_Lines = "" lineNoStart = 1 lineNos = false lineNumbersInTable = true noClasses = true style = "emacs" tabWidth = 4 [markup.tableOfContents] endLevel = 3 ordered = false startLevel = 2 [frontmatter] date = ["date", ":filename", "publishDate", "lastmod"] [permalinks] blog = "/:section/:year/:month/:day/:slug/" [sitemap] filename = "sitemap.xml" priority = 0.75 # Be explicit about the output formats. We (currently) only want an RSS feed for the home page. [outputs] home = [ "HTML", "RSS", "HEADERS" ] page = [ "HTML"] section = [ "HTML", "print" ] # Add a "text/netlify" media type for auto-generating the _headers file [mediaTypes] [mediaTypes."text/netlify"] delimiter = "" [outputFormats] [outputFormats.RSS] baseName = "feed" # _headers file output (uses the template at layouts/index.headers) [outputFormats.HEADERS] mediatype = "text/netlify" baseName = "_headers" isPlainText = true notAlternative = true # Image processing configuration. [imaging] resampleFilter = "CatmullRom" quality = 75 anchor = "smart" [services] [services.googleAnalytics] # Fake ID in support of [params.ui.feedback]. The real GA ID is set in the Netlify config. id = "UA-00000000-0" [params] copyright_k8s = "The Kubernetes Authors" copyright_linux = "Copyright © 2020 The Linux Foundation ®." # privacy_policy = "https://policies.google.com/privacy" # First one is picked as the Twitter card image if not set on page. # images = ["images/project-illustration.png"] # Menu title if your navbar has a versions selector to access old versions of your site. # This menu appears only if you have at least one [params.versions] set. version_menu = "Versions" time_format_blog = "Monday, January 02, 2006" time_format_default = "January 02, 2006 at 3:04 PM PST" description = "Production-Grade Container Orchestration" showedit = true latest = "v1.26" fullversion = "v1.26.0" version = "v1.26" githubbranch = "main" docsbranch = "main" deprecated = false currentUrl = "https://kubernetes.io/docs/home/" nextUrl = "https://kubernetes-io-vnext-staging.netlify.com/" # See codenew shortcode githubWebsiteRaw = "raw.githubusercontent.com/kubernetes/website" # GitHub repository link for editing a page and opening issues. github_repo = "https://github.com/kubernetes/website" # Searching k8s_search = true # The following search parameters are specific to Docsy's implementation. Kubernetes implementes its own search-related partials and scripts. # Google Custom Search Engine ID. Remove or comment out to disable search. #gcs_engine_id = "011737558837375720776:fsdu1nryfng" # Enable Algolia DocSearch algolia_docsearch = false # Enable Lunr.js offline search offlineSearch = false # Official CVE feed bucket URL cveFeedBucket = "https://storage.googleapis.com/k8s-cve-feed/official-cve-feed.json" [params.pushAssets] css = [ "callouts", "styles" ] js = [ "script" ] [[params.versions]] fullversion = "v1.26.0" version = "v1.26" githubbranch = "v1.26.0" docsbranch = "main" url = "https://kubernetes.io" [[params.versions]] fullversion = "v1.25.5" version = "v1.25" githubbranch = "v1.25.5" docsbranch = "release-1.25" url = "https://v1-25.docs.kubernetes.io" [[params.versions]] fullversion = "v1.24.9" version = "v1.24" githubbranch = "v1.24.9" docsbranch = "release-1.24" url = "https://v1-24.docs.kubernetes.io" [[params.versions]] fullversion = "v1.23.15" version = "v1.23" githubbranch = "v1.23.15" docsbranch = "release-1.23" url = "https://v1-23.docs.kubernetes.io" [[params.versions]] fullversion = "v1.22.17" version = "v1.22" githubbranch = "v1.22.17" docsbranch = "release-1.22" url = "https://v1-22.docs.kubernetes.io" # User interface configuration [params.ui] # Enable to show the side bar menu in its compact state. sidebar_menu_compact = false # Show expand/collapse icon for sidebar sections. sidebar_menu_foldable = true # https://github.com/gohugoio/hugo/issues/8918#issuecomment-903314696 sidebar_cache_limit = 1 # Set to true to disable breadcrumb navigation. breadcrumb_disable = false # Set to true to hide the sidebar search box (the top nav search box will still be displayed if search is enabled) sidebar_search_disable = false # Set to false if you don't want to display a logo (/assets/icons/logo.svg) in the top nav bar navbar_logo = true # Set to true to disable the About link in the site footer footer_about_disable = false # Adds a H2 section titled "Feedback" to the bottom of each doc. The responses are sent to Google Analytics as events. # This feature depends on [services.googleAnalytics] and will be disabled if "services.googleAnalytics.id" is not set. # If you want this feature, but occasionally need to remove the "Feedback" section from a single page, # add "hide_feedback: true" to the page's front matter. [params.ui.feedback] enable = true # The responses that the user sees after clicking "yes" (the page was helpful) or "no" (the page was not helpful). yes = 'Glad to hear it! Please tell us how we can improve.' no = 'Sorry to hear that. Please tell us how we can improve.' [params.links] # End user relevant links. These will show up on left side of footer and in the community page if you have one. [[params.links.user]] name = "User mailing list" url = "https://discuss.kubernetes.io" icon = "fa fa-envelope" desc = "Discussion and help from your fellow users" [[params.links.user]] name = "Twitter" url = "https://twitter.com/kubernetesio" icon = "fab fa-twitter" desc = "Follow us on Twitter to get the latest news!" [[params.links.user]] name = "Calendar" url = "https://calendar.google.com/calendar/embed?src=calendar%40kubernetes.io" icon = "fas fa-calendar-alt" desc = "Google Calendar for Kubernetes" [[params.links.user]] name = "Youtube" url = "https://youtube.com/kubernetescommunity" icon = "fab fa-youtube" desc = "Youtube community videos" # Developer relevant links. These will show up on right side of footer and in the community page if you have one. [[params.links.developer]] name = "GitHub" url = "https://github.com/kubernetes/kubernetes" icon = "fab fa-github" desc = "Development takes place here!" [[params.links.developer]] name = "Slack" url = "https://slack.k8s.io" icon = "fab fa-slack" desc = "Chat with other project developers" [[params.links.developer]] name = "Contribute" url = "https://git.k8s.io/community/contributors/guide" icon = "fas fa-edit" desc = "Contribute to the Kubernetes website" [[params.links.developer]] name = "Stack Overflow" url = "https://stackoverflow.com/questions/tagged/kubernetes" icon = "fab fa-stack-overflow" desc = "Practical questions and curated answers" # Language definitions. [languages] [languages.en] title = "Kubernetes" description = "Production-Grade Container Orchestration" languageName = "English" # Weight used for sorting. weight = 1 languagedirection = "ltr" [languages.zh-cn] title = "Kubernetes" description = "生产级别的容器编排系统" languageName = "中文 (Chinese)" languageNameLatinScript = "Chinese" weight = 2 contentDir = "content/zh-cn" languagedirection = "ltr" [languages.zh-cn.params] time_format_blog = "2006.01.02" language_alternatives = ["en"] [languages.ko] title = "Kubernetes" description = "운영 수준의 컨테이너 오케스트레이션" languageName = "한국어 (Korean)" languageNameLatinScript = "Korean" weight = 3 contentDir = "content/ko" languagedirection = "ltr" [languages.ko.params] time_format_blog = "2006.01.02" language_alternatives = ["en"] [languages.ja] title = "Kubernetes" description = "プロダクショングレードのコンテナ管理基盤" languageName = "日本語 (Japanese)" languageNameLatinScript = "Japanese" weight = 4 contentDir = "content/ja" languagedirection = "ltr" [languages.ja.params] time_format_blog = "2006.01.02" language_alternatives = ["en"] [languages.fr] title = "Kubernetes" description = "Solution professionnelle d’orchestration de conteneurs" languageName = "Français (French)" languageNameLatinScript = "Français" weight = 5 contentDir = "content/fr" languagedirection = "ltr" [languages.fr.params] time_format_blog = "02.01.2006" # A list of language codes to look for untranslated content, ordered from left to right. language_alternatives = ["en"] [languages.it] title = "Kubernetes" description = "Orchestrazione di Container in produzione" languageName = "Italiano (Italian)" languageNameLatinScript = "Italiano" weight = 6 contentDir = "content/it" languagedirection = "ltr" [languages.it.params] time_format_blog = "02.01.2006" # A list of language codes to look for untranslated content, ordered from left to right. language_alternatives = ["en"] [languages.no] title = "Kubernetes" description = "Production-Grade Container Orchestration" languageName = "Norsk (Norwegian)" languageNameLatinScript = "Norsk" weight = 7 contentDir = "content/no" languagedirection = "ltr" [languages.no.params] time_format_blog = "02.01.2006" # A list of language codes to look for untranslated content, ordered from left to right. language_alternatives = ["en"] [languages.de] title = "Kubernetes" description = "Produktionsreife Container-Orchestrierung" languageName = "Deutsch (German)" languageNameLatinScript = "Deutsch" weight = 8 contentDir = "content/de" languagedirection = "ltr" [languages.de.params] time_format_blog = "02.01.2006" # A list of language codes to look for untranslated content, ordered from left to right. language_alternatives = ["en"] [languages.es] title = "Kubernetes" description = "Orquestación de contenedores para producción" languageName = "Español (Spanish)" languageNameLatinScript = "Español" weight = 9 contentDir = "content/es" languagedirection = "ltr" [languages.es.params] time_format_blog = "02.01.2006" # A list of language codes to look for untranslated content, ordered from left to right. language_alternatives = ["en"] [languages.pt-br] title = "Kubernetes" description = "Orquestração de contêineres em nível de produção" languageName = "Português (Portuguese)" languageNameLatinScript = "Português" weight = 10 contentDir = "content/pt-br" languagedirection = "ltr" [languages.pt-br.params] time_format_blog = "02.01.2006" # A list of language codes to look for untranslated content, ordered from left to right. language_alternatives = ["en"] [languages.id] title = "Kubernetes" description = "Orkestrasi Kontainer dengan Skala Produksi" languageName ="Bahasa Indonesia" languageNameLatinScript = "Bahasa Indonesia" weight = 11 contentDir = "content/id" languagedirection = "ltr" [languages.id.params] time_format_blog = "02.01.2006" # A list of language codes to look for untranslated content, ordered from left to right. language_alternatives = ["en"] [languages.hi] title = "Kubernetes" description = "प्रोडक्शन-ग्रेड कंटेनर ऑर्केस्ट्रेशन" languageName = "हिन्दी (Hindi)" languageNameLatinScript = "Hindi" weight = 12 contentDir = "content/hi" languagedirection = "ltr" [languages.hi.params] time_format_blog = "02.01.2006" # A list of language codes to look for untranslated content, ordered from left to right. language_alternatives = ["en"] [languages.vi] title = "Kubernetes" description = "Giải pháp điều phối container trong môi trường production" languageName = "Tiếng Việt (Vietnamese)" languageNameLatinScript = "Tiếng Việt" contentDir = "content/vi" weight = 13 languagedirection = "ltr" [languages.ru] title = "Kubernetes" description = "Первоклассная оркестрация контейнеров" languageName = "Русский (Russian)" languageNameLatinScript = "Russian" weight = 14 contentDir = "content/ru" languagedirection = "ltr" [languages.ru.params] time_format_blog = "02.01.2006" # A list of language codes to look for untranslated content, ordered from left to right. language_alternatives = ["en"] [languages.pl] title = "Kubernetes" description = "Produkcyjny system zarządzania kontenerami" languageName = "Polski (Polish)" languageNameLatinScript = "Polski" weight = 15 contentDir = "content/pl" languagedirection = "ltr" [languages.pl.params] time_format_blog = "01.02.2006" # A list of language codes to look for untranslated content, ordered from left to right. language_alternatives = ["en"] [languages.uk] title = "Kubernetes" description = "Довершена система оркестрації контейнерів" languageName = "Українська (Ukrainian)" languageNameLatinScript = "Ukrainian" weight = 16 contentDir = "content/uk" languagedirection = "ltr" [languages.uk.params] time_format_blog = "02.01.2006" # A list of language codes to look for untranslated content, ordered from left to right. language_alternatives = ["en"]

This is a Feature Request rename to Why is this needed we update to 0.110.0 /assign
is a thing now, so: /triage accepted


Question: ## {{% heading "whatsnext" %}} <del> * [attaching handlers to Container lifecycle events](/ja/docs/tasks/configure-pod-container/attach-handler-lifecycle-event/)のハンズオンをやってみる </del> <ins> * [コンテナライフサイクルイベントへのハンドラー紐付け](/ja/docs/tasks/configure-pod-container/attach-handler-lifecycle-event/)のハンズオンをやってみる </ins> <del> * [Configure Liveness, Readiness and Startup Probes](/ja/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/)のハンズオンをやってみる </del> <ins> * [Liveness Probe、Readiness ProbeおよびStartup Probeを使用する](/ja/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/)のハンズオンをやってみる </ins> <del> * [Container lifecycle hooks](/ja/docs/concepts/containers/container-lifecycle-hooks/)についてもっと学ぶ </del> <ins> * [コンテナライフサイクルフック](/ja/docs/concepts/containers/container-lifecycle-hooks/)についてもっと学ぶ </ins> <del> * APIのPod/コンテナステータスの詳細情報は[PodStatus](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#podstatus-v1-core)および[ContainerStatus](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#containerstatus-v1-core)を参照してください </del> <ins> * APIにおけるPodとコンテナのステータスに関する詳細情報は、Podの[`.status`](/docs/reference/kubernetes-api/workload-resources/pod-v1/#PodStatus)に書かれているAPIリファレンスドキュメントを参照してください。 </ins>

This is a Feature Request What would you like to be We need to update content/ja/docs/concepts/workloads/pods/pod- according to the English text, because it is outdated. Why is this needed content/ja/docs/concepts/workloads/pods/pod- is outdated. For example, there is no description of PodHasNetwork(alpha feature). Comments /language ja /assign
/triage accepted


Follow PR
/language ja
/assign
We can close this issue by
/close
Closing this issue. <detailsIn response to : /close Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details


Question: `replace`        | `kubectl replace -f FILENAME` |  基于文件或标准输入替换资源。 `rollout`    | `kubectl rollout SUBCOMMAND [options]` | 管理资源的上线。有效的资源类型包括：Deployment、 DaemonSet 和 StatefulSet。 `run`        | kubectl run NAME --image=image [--env="key=value"] [--port=port] [--dry-run=server | client | none] [--overrides=inline-json] [flags] | 在集群上运行指定的镜像。    `scale`        | kubectl scale (-f FILENAME | TYPE NAME | TYPE/NAME) --replicas=COUNT [--resource-version=version] [--current-replicas=count] [flags] | 更新指定副本控制器的大小。 `set`    | `kubectl set SUBCOMMAND [options]` | 配置应用资源。 `taint`    | `kubectl taint NODE NAME KEY_1=VAL_1:TAINT_EFFECT_1 ... KEY_N=VAL_N:TAINT_EFFECT_N [options]` | 更新一个或多个节点上的污点。

web
/retitle [zh-cn] Fix table formatting errors on the kubectl page
/triage accepted


Question: kubectl delete deployment hello-node ``` <del> (オプション)Minikubeの仮想マシン(VM)を停止します: </del> <ins> (オプション)minikubeの仮想マシン(VM)を停止します: </ins> ```shell minikube stop ``` <del> (オプション)MinikubeのVMを削除します: </del> <ins> (オプション)minikubeのVMを削除します: </ins> ```shell minikube delete

This is a Feature Request In the documentation available in , as well as in the link, the term is written as . I'd like to suggest updating it to to align with the and . <!-- 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 occurrences of to . Why is this needed Using the incorrect casing can be misleading, especially for newcomers. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --
/assign
/language ja
/triage accepted


Question: role: db ingress: - from: <del> podSelector: matchLabels: role: frontend </del> <ins> - podSelector: matchLabels: role: frontend </ins> ports: - protocol: tcp port: 6379

When I try creating the example given in that page, I get this error: Indeed, after I change the value of from a map to a list containing that map, the create succeeds. Here is the corrected source:


Question:
After experimenting with another container orchestration platform and "breaking it in very painful ways," Lynch says, the team began experimenting with Kubernetes in mid-2016 and found that it "answered all the questions that we had." {{< /case-studies/quote >}}
Within a couple months, they had a stable cluster for their internal use, and began rolling out Kubernetes for production. They also added Zipkin and CNCF projects Prometheus and fluentd to their cloud native stack. "We switched to Kubernetes, a new world, and we revamped all our other tooling as well," says Lynch. "It allowed us to streamline our process, so we can now easily create an entire microservice project from templates, generate the code and deployment pipeline for that, generate the Docker file, and then immediately just ship a workable, deployable project to Kubernetes." Deployments across Dev/QA/Stage/Prod were also "simplified drastically," Lynch adds. "Now there is little configuration variation."

Within a couple months, they had a stable cluster for their internal use, and began rolling out Kubernetes for production. They also added Zipkin and CNCF projects Prometheus and fluentd to their cloud native stack. "We switched to Kubernetes, a new world, and we revamped all our other tooling as well," says Lynch. "It allowed us to streamline our process, so we can now easily create an entire microservice project from templates, generate the code and deployment pipeline for that, generate the Dockerfile, and then immediately just ship a workable, deployable project to Kubernetes." Deployments across Dev/QA/Stage/Prod were also "simplified drastically," Lynch adds. "Now there is little configuration variation."

And the whole process takes only five minutes, an almost 85% reduction in time compared to their VM deployment. "From end to end that probably took half an hour, and that's not accounting for the fact that an infrastructure engineer would be responsible for doing that, so there's some business delay in there as well."

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: ## コンテナのステータス {#container-states} <del> Pod全体の[フェーズ](#pod-phase)と同様に、KubernetesはPod内の各コンテナの状態を追跡します。[container lifecycle hooks](/docs/concepts/containers/container-lifecycle-hooks/)を使用して、コンテナのライフサイクルの特定のポイントで実行するイベントをトリガーできます。 </del> <ins> Pod全体の[フェーズ](#pod-phase)と同様に、KubernetesはPod内の各コンテナの状態を追跡します。[container lifecycle hooks](/ja/docs/concepts/containers/container-lifecycle-hooks/)を使用して、コンテナのライフサイクルの特定のポイントで実行するイベントをトリガーできます。 </ins> Podが{{< glossary_tooltip text="scheduler" term_id="kube-scheduler" >}}によってNodeに割り当てられると、kubeletは{{< glossary_tooltip text="container runtime" term_id="container-runtime" >}}を使用してコンテナの作成を開始します。コンテナの状態は`Waiting`、`Running`または`Terminated`の3ついずれかです。

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. --Update some links and fix some expressions. Why is this needed Some of the links have already been translated Also, some expressions were not official. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/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: This command checks that your cluster can be upgraded, and fetches the versions you can upgrade to. <del> {{< note >}} `kubeadm upgrade` also automatically renews the certificates that it manages on this node. To opt-out of certificate renewal the flag `--certificate-renewal=false` can be used. For more information see the [certificate management guide](/docs/tasks/administer-cluster/kubeadm/kubeadm-certs). {{</ note >}} </del> <ins> {{< note >}} `kubeadm upgrade` also automatically renews the certificates that it manages on this node. To opt-out of certificate renewal the flag `--certificate-renewal=false` can be used. For more information see the [certificate management guide](/docs/tasks/administer-cluster/kubeadmkubeadm-certs). {{</ note >}} </ins> <del> 1.  Choose a version to upgrade to, and run the appropriate command. For example: </del> <ins> -  Choose a version to upgrade to, and run the appropriate command. For example: </ins> ```shell # replace x with the patch version you picked for this upgrade

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: ## Creating a Deployment <del> Before creating a Deployment define an [environment variable](/docs/tasks/inject-data-application/define-environment-variable-container/#define-an-environment-variable-for-a-container) for a container. </del> The following is an example of a Deployment. It creates a ReplicaSet to bring up three `nginx` Pods: {{< codenew file="controllers/nginx-deployment.yaml" >}}

It is unclear what is meant by The statement appears directly under the heading "Creating a Deployment." It is confusing, and it is unclear what relevance defining an "environment variable" has to do with a deployment. Could it be that the author intended to present an action item of defining a pod, and linked to another article that coincidentally contained markup to do so? Suggestion is to clean up the paragraph, and link it to an appropriate article on defining pods, if so.
/sig apps
/retitle Unclear text in “Creating a Deployment” section of Deployment concept
/language en /help /triage accepted
I recommend removing from the page. That's a small fix that doesn't need us to work on the rest of
/assign
page to be updated:
Looks similar (possibly duplicate) of issue we already have
True. /triage duplicate
/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
/remove-help Oops


Question: In Kubernetes, there are two ways to expose Pod and container fields to a running container: <del> * as [environment variables](/docs/tasks/inject-data-application/environment-variable-expose-pod-information/#the-downward-api) </del> <ins> * as [environment variables](/docs/tasks/inject-data-application/environment-variable-expose-pod-information/) </ins> * as [files in a `downwardAPI` volume](/docs/tasks/inject-data-application/downward-api-volume-expose-pod-information/) Together, these two ways of exposing Pod and container fields are called the

This is a Bug Report <!--Required Information--Problem: The link is dead. The content from the section seems moved into top of the document and glossary in . Proposed Solution: remove fragment from the link change link to or Page to Update: /docs/concepts/workloads/pods/downward-api /docs/tasks/inject-data-application/downward-api-volume-expose-pod-information /docs/tasks/job/indexed-parallel-processing-static
/assign
/language en /triage accepted /help We should find existing hyperlinks to and replace those with links to
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 : /language en /triage accepted /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
/unassign As has already opened a PR
/assign
GitHub didn't allow me to assign the following users: hs0210. Note that only , repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. For more information please see <detailsIn response to : /assign 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


Question: ## Usage Summary <del> * `--network-plugin=cni` specifies that we use the `cni` network plugin with actual CNI plugin binaries located in `--cni-bin-dir` (default `/opt/cni/bin`) and CNI plugin configuration located in `--cni-conf-dir` (default `/etc/cni/net.d`). </del> <ins> Once the Kubelet is installed and communicating with the Kubernetes API Server, a CNI plugin can be installed using the instructions for that plugin. </ins> ## {{% heading "whatsnext" %}}

! 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: <link href="/docs/tutorials/kubernetes-basics/public/css/styles.css" rel="stylesheet"> <link href="/docs/tutorials/kubernetes-basics/public/css/overrides.css" rel="stylesheet"> <del> <script src="https://katacoda.com/embed.js"></script> </del> <ins> {{< katacoda-tutorial >}} </ins> <div class="layout" id="top">

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 For pages that use Katacoda, add a warning about its removal. Why is this needed Prompted by and Comments /priority critical-urgent /language en /triage accepted


Question: ### Volume Binding Mode <del> The `volumeBindingMode` field controls when [volume binding and dynamic provisioning](/docs/concepts/storage/persistent-volumes/#provisioning) should occur. When unset, "Immediate" mode is used by default. </del> <ins> The `volumeBindingMode` field controls when [volume binding and dynamic provisioning](/docs/concepts/storage/persistent-volumes/#provisioning) should occur. When unset, "Immediate" mode is used by default. </ins> The `Immediate` mode indicates that volume binding and dynamic provisioning occurs once the PersistentVolumeClaim is created. For storage

There's a section for ReclaimPolicy, which states that this can be or . It is not clear as to what those states mean, there's NO explanation. I was researching how to expand disk, and one guide says that the must be , but I cannot find reference as to what this means. My expectation was that these would be explained what they mean, rather than this is the only do option.
Page related to issue: /retitle Lack of explanation for options - Retain and Delete /language en
These concepts are well explained in 'concepts/storage/persistent-'. Maybe a pointer or two suffices?
Please refer link here you will find the brief introduction about the retain or delete. I think this link will be helpful to understand.
/assign
/triage accepted


Question: See [Certificate Signing Requests](/docs/reference/access-authn-authz/certificate-signing-requests/) for more information on the permissions required to perform different actions on CertificateSigningRequest resources. <del> ### CertificateSubjectRestrictions {#certificatesubjectrestrictions} </del> <ins> ### CertificateSubjectRestriction {#certificatesubjectrestriction} </ins> This admission controller observes creation of CertificateSigningRequest resources that have a `spec.signerName` of `kubernetes.io/kube-apiserver-client`. It rejects any request that specifies a 'group' (or 'organization attribute')

Simple documentation issue: Section for "CertificateSubjectRestriction" admission controller is "CertificateSubjectRestrictions". The appended 's' is not valid and will prevent apiserver startup if used in --disable-admission-plugins. Note: plugin is listed correctly in the 'defaults' list.
Fixed by /close
Closing this issue. <detailsIn response to : Fixed by /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
/triage accepted /language en


Question: また、[`kubectl`リファレンスドキュメント](/ja/docs/reference/kubectl/)も参照できます。 <del> ## Minikube </del> <ins> ## minikube </ins> <del> [Minikube](https://minikube.sigs.k8s.io/)は、Kubernetesをローカルで実行するツールです。MinikubeはシングルノードのKubernetesクラスターをパーソナルコンピューター上(Windows、macOS、Linux PCを含む)で実行することで、Kubernetesを試したり、日常的な開発作業のために利用できます。 </del> <ins> [minikube](https://minikube.sigs.k8s.io/)は、Kubernetesをローカルで実行するツールです。minikubeはシングルノードのKubernetesクラスターをパーソナルコンピューター上(Windows、macOS、Linux PCを含む)で実行することで、Kubernetesを試したり、日常的な開発作業のために利用できます。 </ins> ツールのインストールについて知りたい場合は、公式の[Get Started!](https://minikube.sigs.k8s.io/docs/start/)のガイドに従ってください。 <del> Minikubeが起動したら、[サンプルアプリケーションの実行](/ja/docs/tutorials/hello-minikube/)を試すことができます。 </del> <ins> minikubeが起動したら、[サンプルアプリケーションの実行](/ja/docs/tutorials/hello-minikube/)を試すことができます。 </ins> ## kind <del> Minikubeと同じように、[kind](https://kind.sigs.k8s.io/docs/)もローカルコンピューター上でKubernetesを実行するツールです。Minikubeとは違い、kindは1種類のコンテナランタイム上でしか動作しません。実行には[Docker](https://docs.docker.com/get-docker/)のインストールと設定が必要です。 </del> <ins> minikubeと同じように、[kind](https://kind.sigs.k8s.io/docs/)もローカルコンピューター上でKubernetesを実行するツールです。minikubeとは違い、kindは1種類のコンテナランタイム上でしか動作しません。実行には[Docker](https://docs.docker.com/get-docker/)のインストールと設定が必要です。 </ins> [Quick Start](https://kind.sigs.k8s.io/docs/user/quick-start/)に、kindの起動に必要な手順が説明されています。

This is a Feature Request In the documentation available in , as well as in the link, the term is written as . I'd like to suggest updating it to to align with the and . <!-- 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 occurrences of to . Why is this needed Using the incorrect casing can be misleading, especially for newcomers. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --
/assign
/language ja
/triage accepted


Question: certificates by requesting them from the `certificates.k8s.io` API. One known limitation is that the CSRs (Certificate Signing Requests) for these certificates cannot be automatically approved by the default signer in the kube-controller-manager - <del> [`kubernetes.io/kubelet-serving`](https://kubernetes.io/docs/reference/access-authn-authz/certificate-signing-requests/#kubernetes-signers). </del> <ins> [`kubernetes.io/kubelet-serving`](/docs/reference/access-authn-authz/certificate-signing-requests/#kubernetes-signers). </ins> This will require action from the user or a third party controller. These CSRs can be viewed using:

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 href of contains unwanted . A slash () is missing in the href of . Proposed Solution: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language en /assign
/triage accepted


Question: <ins> #!/bin/bash #!/usr/bin/env bash # This script reproduces what the kubelet does # to calculate memory.available relative to root cgroup. # current memory usage memory_capacity_in_kb=$(cat /proc/meminfo | grep MemTotal | awk '{print $2}') memory_capacity_in_bytes=$((memory_capacity_in_kb * 1024)) memory_usage_in_bytes=$(cat /sys/fs/cgroup/memory/memory.usage_in_bytes) memory_total_inactive_file=$(cat /sys/fs/cgroup/memory/memory.stat | grep total_inactive_file | awk '{print $2}') memory_working_set=${memory_usage_in_bytes} if [ "$memory_working_set" -lt "$memory_total_inactive_file" ]; then memory_working_set=0 else memory_working_set=$((memory_usage_in_bytes - memory_total_inactive_file)) fi memory_available_in_bytes=$((memory_capacity_in_bytes - memory_working_set)) memory_available_in_kb=$((memory_available_in_bytes / 1024)) memory_available_in_mb=$((memory_available_in_kb / 1024)) echo "memory.capacity_in_bytes $memory_capacity_in_bytes" echo "memory.usage_in_bytes $memory_usage_in_bytes" echo "memory.total_inactive_file $memory_total_inactive_file" echo "memory.working_set $memory_working_set" echo "memory.available_in_bytes $memory_available_in_bytes" echo "memory.available_in_kb $memory_available_in_kb" echo "memory.available_in_mb $memory_available_in_mb" </ins>

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 is a broken link to script in tasks/administer-cluster/out-of- file. At 44 line: Proposed Solution: Move the script file to examples directory. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language en
/assign


Question: body { background-color: white; <ins> a { color: $blue; } </ins> } section {

This is a Bug Report Links within the tab component are not displaying using the site link color. Problem: The color of links within tab components is defaulting to . The link is inheriting the color value from jquery-ui- Proposed Solution: Update the style for ui-widget-content -a Page to Update: Start by looking at . Examples: See link in Flatcar Container Linux tab in Look as the "vSphere" tab at the bottom of the page.
Related to PR .
/kind bug /priority backlog /area web-development Feel free to reprioritize
/assign


Question: Download the kubectl checksum file: ```powershell <del> curl -LO https://dl.k8s.io/{{< param "fullversion" >}}/bin/windows/amd64/kubectl.exe.sha256 </del> <ins> curl -LO "https://dl.k8s.io/{{< param "fullversion" >}}/bin/windows/amd64/kubectl.exe.sha256" </ins> ``` Validate the kubectl binary against the checksum file:

Very basic step "Install kubectl binary with curl on Windows" Response seems good: But .exe is actually XML, giving download error: Hard to realize and quite unfriendly! Thanks
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 bug There are multiple broken links on this page. It seems the links on this page is missing the version from it
/assign


Question: with `NoExecute` effect. If the fault condition returns to normal the kubelet or node controller can remove the relevant taint(s). <ins> In some cases when the node is unreachable, the API server is unable to communicate with the kubelet on the node. The decision to delete the pods cannot be communicated to the kubelet until communication with the API server is re-established. In the meantime, the pods that are scheduled for deletion may continue to run on the partitioned node. </ins> {{< note >}} The control plane limits the rate of adding node new taints to nodes. This rate limiting manages the number of evictions that are triggered when many nodes become unreachable at

This page talks about but the page referred does not contain anything about . Looks like either Nodes is outdated or kube-controller-manager is missing this documentation.
Page:
was deprecated in k8s v1.26 and will remove in k8s v1.27 Here is the PR:
As it is deprecated we have to mention this as a note in the docs for v1.26 and in v1.27, remove this from the docs. Let's wait for others members, what they think about it.
/kind bug /sig apps
/retitle Stale or incorrect information in Nodes concept page
/remove-sig apps It's nice if people who deprecate a thing also track a docs update issue. However, I wouldn't expect SIG Apps to pick this up.
yeah, that will be really helpful.
/triage accepted
Could you please take a look?
/triage accepted
/assign
thanks for the PR. It is Ok for v1.27. But I have one concern regarding v1.26 if we click on as mentioned above, we can't find as it is deprecated in v1.26. Either we have to remove this from v1.26 also or mention the Note in v1.26 docs regarding the depreciation.
It is mentioned under till k8s v1.25. Here is the following link for it: https://v1-
Hi , Your thoughts on this
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
closing this issue, as it was resolved by PR /close
Closing this issue. <detailsIn response to : closing this issue, as it was resolved by PR 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: <!-- ## Use foreground cascading deletion {#use-foreground-cascading-deletion} <del> By default, Kubernetes uses [background cascading deletion](/docs/concepts/workloads/controllers/garbage-collection/#background-deletion) </del> <ins> By default, Kubernetes uses [background cascading deletion](/docs/concepts/architecture/garbage-collection/#background-deletion) </ins> to delete dependents of an object. You can switch to foreground cascading deletion using either `kubectl` or the Kubernetes API, depending on the Kubernetes version your cluster runs. {{<version-check>}} --> ## 使用前台级联删除    {#use-foreground-cascading-deletion} <del> 默认情况下，Kubernetes 使用[后台级联删除](/zh/docs/concepts/workloads/controllers/garbage-collection/#background-deletion) </del> <ins> 默认情况下，Kubernetes 使用[后台级联删除](/zh/docs/concepts/architecture/garbage-collection/#background-deletion) </ins> 以删除依赖某对象的其他对象。取决于你的集群所运行的 Kubernetes 版本， 你可以使用 `kubectl` 或者 Kubernetes API 来切换到前台级联删除。 {{<version-check>}}

There is a bug: ,%E4%BA%86%E8%A7%A3%E5%9E%83%E5%9C%BE%E6%94%B6%E9%9B%86.,-%E5%8F%8D%E9%A6%88 This hyperlink is 404, it should be ""
/assign
/triage accepted
The issue was solved by PR . If there is any problem, please give feedback again. /close
Closing this issue. <detailsIn response to : The issue was solved by PR . If there is any problem, please give feedback again. /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: These guides are maintained by community members, cover specific platforms and use cases, and experiment with different ways of configuring Kubernetes on CoreOS. <del> [**Multi-node Cluster**](/docs/getting-started-guides/coreos/coreos_multinode_cluster) Set up a single master, multi-worker cluster on your choice of platform: AWS, GCE, or VMware Fusion. <hr/> </del> [**Easy Multi-node Cluster on Google Compute Engine**](https://github.com/rimusz/coreos-multi-node-k8s-gce/blob/master/README.md) Scripted installation of a single master, multi-worker cluster on GCE. Kubernetes components are managed by [fleet](https://github.com/coreos/fleet).

A user linked to this guide from an issue: I believe that guide is unmaintained. It still specifies k8s 1.1.2. can we delete?
Thank you. Yes, this guide was unmaintained and community contributed. I am OK with this change. devin-donnelly wrote:


Question: Create the Pod: --> <del> 在这个配置文件中，你可以看到 Pod 有一个 `downwardAPI` 类型的卷，并且挂载到容器的 `/etc/podinfo` 目录。 </del> <ins> 在这个配置文件中，你可以看到 Pod 有一个 `downwardAPI` 类型的卷，并且挂载到容器的 `/etc/podinfo` 目录。 </ins> 查看 `downwardAPI` 下面的 `items` 数组。每个数组元素都是一个 DownwardAPIVolumeFile。

the file labels and annotations should be in the directory /etc/podinfo not /etc !
Hi What's the URL of the web page that isn't right? /triage needs-information
/triage accepted
/assign


Question: runtime_path = "${PATH_TO_BINARY}" ``` <del> 詳細はCRI-Oの[設定に関するドキュメント](https://raw.githubusercontent.com/cri-o/cri-o/9f11d1d/docs/crio.conf.5.md)を参照してください。 </del> <ins> 詳細はCRI-Oの[設定に関するドキュメント](https://github.com/cri-o/cri-o/blob/master/docs/crio.conf.5.md)を参照してください。 </ins> ## スケジューリング {#scheduling} {{< feature-state for_k8s_version="v1.16" state="beta" >}} <del> Kubernetes 1.16では、RuntimeClassは`scheduling`フィールドを使ったクラスター内での異なる設定をサポートしています。 このフィールドによって、設定されたRuntimeClassをサポートするノードに対してPodがスケジュールされることを保証できます。 スケジューリングをサポートするためにはRuntimeClass [アドミッションコントローラー](/docs/reference/access-authn-authz/admission-controllers/#runtimeclass)を有効にしなければなりません。(1.16ではデフォルトです) </del> <ins> RuntimeClassの`scheduling`フィールドを指定することで、設定されたRuntimeClassをサポートするノードにPodがスケジューリングされるように制限することができます。 `scheduling`が設定されていない場合、このRuntimeClassはすべてのノードでサポートされていると仮定されます。 </ins> 特定のRuntimeClassをサポートしているノードへPodが配置されることを保証するために、各ノードは`runtimeclass.scheduling.nodeSelector`フィールドによって選択される共通のラベルを持つべきです。 RuntimeClassのnodeSelectorはアドミッション機能によりPodのnodeSelectorに統合され、効率よくノードを選択します。

This is a Feature Request What would you like to be We need to update content/ja/docs/concepts/containers/runtime- according to the English text, because it is outdated. Why is this needed content/ja/docs/concepts/containers/runtime- is outdated. Comments /language ja /assign
/triage accepted


Question: ### container.seccomp.security.alpha.kubernetes.io/[NAME] {#container-seccomp-security-alpha-kubernetes-io} This annotation has been deprecated since Kubernetes v1.19 and will become non-functional in v1.25. <del> The tutorial [Restrict a Container's Syscalls with seccomp](/docs/tutorials/clusters/seccomp/) takes </del> <ins> The tutorial [Restrict a Container's Syscalls with seccomp](/docs/tutorials/security/seccomp/) takes </ins> you through the steps you follow to apply a seccomp profile to a Pod or to one of its containers. That tutorial covers the supported mechanism for configuring seccomp in Kubernetes, based on setting `securityContext` within the Pod's `.spec`.

This is a Bug Report There is a link /docs/tutorials/clusters/seccomp on line 481 of the page content endocsreferencelabels-annotations-,but this link does not exist. <!--Required Information--Problem: There is a link /docs/tutorials/clusters/seccomp on line 481 of the page contentendocsreferencelabels-annotations-,but this link does not exist. Proposed Solution: commented redirects to We should update so that it hyperlinks to instead. Page to Update: <!--Kubernetes Version:--v1.23 <!--Additional Information:--NA Comments /language zh /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 done, next time we can use in PR description to auto close this. /close
Closing this issue. <detailsIn response to : Already done, next time we can use in PR description to auto close this. 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: <ins> --- title: Container Lifecycle Hooks content_type: concept weight: 30 --- <!-- overview --> Questa pagina descrive come i Container gestiti con kubelet possono utilizzare il lifecycle hook framework dei Container per l'esecuzione di codice eseguito in corrispondenza di alcuni eventi durante il loro ciclo di vita. <!-- body --> ## Overview Analogamente a molti framework di linguaggi di programmazione che hanno degli hooks legati al ciclo di vita dei componenti, come ad esempio Angular, Kubernetes fornisce ai Container degli hook legati al loro ciclo di vita dei Container. Gli hook consentono ai Container di essere consapevoli degli eventi durante il loro ciclo di gestione ed eseguire del codice implementato in un handler quando il corrispondente hook viene eseguito. ## Container hooks Esistono due tipi di hook che vengono esposti ai Container: `PostStart` Questo hook viene eseguito successivamente alla creazione del container. Tuttavia, non vi è garanzia che questo hook venga eseguito prima dell'ENTRYPOINT del container. Non vengono passati parametri all'handler. `PreStop` Questo hook viene eseguito prima della terminazione di un container a causa di una richiesta API o di un evento di gestione, come ad esempio un fallimento delle sonde di liveness/startup, preemption, risorse contese e altro. Una chiamata all'hook di `PreStop` fallisce se il container è in stato terminated o completed e l'hook deve finire prima che possa essere inviato il segnale di TERM per fermare il container. Il conto alla rovescia per la terminazione del Pod (grace period) inizia prima dell'esecuzione dell'hook `PreStop`, quindi indipendentemente dall'esito dell'handler, il container terminerà entro il grace period impostato. Non vengono passati parametri all'handler. Una descrizione più dettagliata riguardante al processo di terminazione dei Pod può essere trovata in [Terminazione dei Pod](/docs/concepts/workloads/pods/pod-lifecycle/#pod-termination). ### Implementazione degli hook handler I Container possono accedere a un hook implementando e registrando un handler per tale hook. Ci sono due tipi di handler che possono essere implementati per i Container: * Exec - Esegue un comando specifico, tipo `pre-stop.sh`, all'interno dei cgroup e namespace del Container. Le risorse consumate dal comando vengono contate sul Container. * HTTP - Esegue una richiesta HTTP verso un endpoint specifico del Container. ### Esecuzione dell'hook handler Quando viene richiamato l'hook legato al lifecycle del Container, il sistema di gestione di Kubernetes esegue l'handler secondo l'azione dell'hook, `httpGet` e `tcpSocket` vengono eseguiti dal processo kubelet, mentre `exec` è eseguito nel Container. Le chiamate agli handler degli hook sono sincrone rispetto al contesto del Pod che contiene il Container. Questo significa che per un hook `PostStart`, l'ENTRYPOINT e l'hook si attivano in modo asincrono. Tuttavia, se l'hook impiega troppo tempo per essere eseguito o si blocca, il container non può raggiungere lo stato di `running`. Gli hook di `PreStop` non vengono eseguiti in modo asincrono dall'evento di stop del container; l'hook deve completare la sua esecuzione prima che l'evento TERM possa essere inviato. Se un hook di `PreStop` si blocca durante la sua esecuzione, la fase del Pod rimarrà `Terminating` finchè il Pod non sarà rimosso forzatamente dopo la scadenza del suo `terminationGracePeriodSeconds`. Questo grace period si applica al tempo totale necessario per effettuare sia l'esecuzione dell'hook di `PreStop` che per l'arresto normale del container. Se, per esempio, il `terminationGracePeriodSeconds` è di 60, e l'hook impiega 55 secondi per essere completato, e il container impiega 10 secondi per fermarsi normalmente dopo aver ricevuto il segnale, allora il container verrà terminato prima di poter completare il suo arresto, poiché `terminationGracePeriodSeconds` è inferiore al tempo totale (55+10) necessario perché queste due cose accadano. Se un hook `PostStart` o `PreStop` fallisce, allora il container viene terminato. Gli utenti dovrebbero mantenere i loro handler degli hook i più leggeri possibili. Ci sono casi, tuttavia, in cui i comandi di lunga durata hanno senso, come il salvataggio dello stato del container prima della sua fine. ### Garanzia della chiamata dell'hook La chiamata degli hook avviene *almeno una volta*, il che significa che un hook può essere chiamato più volte da un dato evento, come per `PostStart` o `PreStop`. Sta all'implementazione dell'hook gestire correttamente questo aspetto. Generalmente, vengono effettuate singole chiamate agli hook. Se, per esempio, la destinazione di hook HTTP non è momentaneamente in grado di ricevere traffico, non c'è alcun tentativo di re invio. In alcuni rari casi, tuttavia, può verificarsi una doppia chiamata. Per esempio, se un kubelet si riavvia nel mentre dell'invio di un hook, questo potrebbe essere chiamato per una seconda volta dopo che il kubelet è tornato in funzione. ### Debugging Hook handlers I log di un handler di hook non sono esposti negli eventi del Pod. Se un handler fallisce per qualche ragione, trasmette un evento. Per il `PostStart`, questo è l'evento di `FailedPostStartHook`, e per il `PreStop`, questo è l'evento di `FailedPreStopHook`. Puoi vedere questi eventi eseguendo `kubectl describe pod <pod_name>`. Ecco alcuni esempi di output di eventi dall'esecuzione di questo comando: ``` Events: 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 ``` ## {{% heading "whatsnext" %}} * Approfondisci [Container environment](/docs/concepts/containers/container-environment/). * Esegui un tutorial su come [definire degli handlers per i Container lifecycle events](/docs/tasks/configure-pod-container/attach-handler-lifecycle-event/). </ins>

I would like to have the "Container Lifecycle Hooks" page to be translated into Italian page /language it /priority important-soon
/remove-priority important-soon /priority important-longterm
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale
/remove-lifecycle stale
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale
/remove-lifecycle stale
Hi I am taking this issue! :smile: /assign /lifecycle active
this can help (you can find specific instructions for the web-site) Ping me if you need help
Hi I have finished my issue! PR ! Let me know!


Question: kubectl describe services example-service ``` <del> which should produce output like this: </del> <ins> which should produce output similar to: </ins> <del> ```bash Name:                   example-service Namespace:              default Labels:                 <none> Annotations:            <none> Selector:               app=example Type:                   LoadBalancer IP:                     10.67.252.103 LoadBalancer Ingress:   192.0.2.89 Port:                   <unnamed> 80/TCP NodePort:               <unnamed> 32445/TCP Endpoints:              10.64.0.4:80,10.64.1.5:80,10.64.2.4:80 Session Affinity:       None Events:                 <none> </del> <ins> ``` Name:                     example-service Namespace:                default Labels:                   app=example Annotations:              <none> Selector:                 app=example Type:                     LoadBalancer IP Families:              <none> IP:                       10.3.22.96 IPs:                      10.3.22.96 LoadBalancer Ingress:     192.0.2.89 Port:                     <unset>  8765/TCP TargetPort:               9376/TCP NodePort:                 <unset>  30593/TCP Endpoints:                172.17.0.3:9376 Session Affinity:         None External Traffic Policy:  Cluster Events:                   <none> </ins> ``` <del> The IP address is listed next to `LoadBalancer Ingress`. </del> <ins> The load balancer's IP address is listed next to `LoadBalancer Ingress`. </ins> {{< note >}} If you are running your service on Minikube, you can find the assigned IP address and port with: <del> {{< /note >}} </del> ```bash minikube service example-service --url ``` <ins> {{< /note >}} </ins> ## Preserving the client source IP <del> Due to the implementation of this feature, the source IP seen in the target container is *not the original source IP* of the client. To enable preservation of the client IP, the following fields can be configured in the service spec (supported in GCE/Google Kubernetes Engine environments): * `service.spec.externalTrafficPolicy` - denotes if this Service desires to route external traffic to node-local or cluster-wide endpoints. There are two available options: Cluster (default) and Local. Cluster obscures the client source IP and may cause a second hop to another node, but should have good overall load-spreading. Local preserves the client source IP and avoids a second hop for LoadBalancer and NodePort type services, but risks potentially imbalanced traffic spreading. * `service.spec.healthCheckNodePort` - specifies the health check node port (numeric port number) for the service. If `healthCheckNodePort` isn't specified, the service controller allocates a port from your cluster's NodePort range. You can configure that range by setting an API server command line option, `--service-node-port-range`. It will use the user-specified `healthCheckNodePort` value if specified by the client. It only has an effect when `type` is set to LoadBalancer and `externalTrafficPolicy` is set to Local. Setting `externalTrafficPolicy` to Local in the Service configuration file activates this feature. </del> <ins> By default, the source IP seen in the target container is *not the original source IP* of the client. To enable preservation of the client IP, the following fields can be configured in the `.spec` of the Service: * `.spec.externalTrafficPolicy` - denotes if this Service desires to route external traffic to node-local or cluster-wide endpoints. There are two available options: `Cluster` (default) and `Local`. `Cluster` obscures the client source IP and may cause a second hop to another node, but should have good overall load-spreading. `Local` preserves the client source IP and avoids a second hop for LoadBalancer and NodePort type Services, but risks potentially imbalanced traffic spreading. * `.spec.healthCheckNodePort` - specifies the health check node port (numeric port number) for the service. If you don't specify `healthCheckNodePort`, the service controller allocates a port from your cluster's NodePort range. You can configure that range by setting an API server command line option, `--service-node-port-range`. The Service will use the user-specified `healthCheckNodePort` value if you specify it, provided that the Service `type` is set to LoadBalancer and `externalTrafficPolicy` is set to `Local`. Setting `externalTrafficPolicy` to Local in the Service manifest activates this feature. For example: </ins> ```yaml apiVersion: v1

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: mentions: (see ) Weights aren't built in to Service / Endpoints / EndpointSlice / Ingress but you can indicate weighting with annotations and similar mechanisms. For example: https://kubernetes- Proposed Solution: Remove the text: Revise to explain that each implementation uses its own mechanisms for weighting and that these are not standardized. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--Kubernetes Version: v1.19 Additional Information: /language en /sig network
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
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
/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
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]:


Question: --> ### cloud-controller-manager <ins> {{< glossary_definition term_id="cloud-controller-manager" length="short" >}} </ins> `cloud-controller-manager` 进运行特定于云平台的控制回路。 如果你在自己的环境中运行 Kubernetes，或者在本地计算机中运行学习环境， 所部属的环境中不需要云控制器管理器。

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: Original text hast been kept along with translated text Proposed Solution: Delete original English text Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--<img width="863" alt="" src="https://user-"
Looks like the is still working even when being commented out. I have encountered this a hundred times when tidying up the Chinese localization, and this is one of the reasons I don't like this shortcode.
/assign


Question: } } <del> <!-- 1.  Create a JSON config file for CA certificate signing request (CSR), for example, `ca-csr.json`. Be sure to replace the values marked with angle brackets with real values you want to use. --> 1.  创建一个 JSON 配置文件，用于 CA 证书签名请求（CSR），例如：`ca-csr.json`。 </del> <ins> <!-- 4.  Create a JSON config file for CA certificate signing request (CSR), for example, `ca-csr.json`. Be sure to replace the values marked with angle brackets with real values you want to use. --> 4.  创建一个 JSON 配置文件，用于 CA 证书签名请求（CSR），例如：`ca-csr.json`。 </ins> 确认用你需要的值替换掉尖括号中的值。 {

Link to The secondary list elements in the page are all "1." , they are not in order, it looks weird
/sig docs
Hi can you please elaborate which page are you talking about?
Sorry, I forgot to check the link in my issue, the correct link is
/language zh /triage accepted /retitle [zh] Wrong list numbering in page FYI: Page to update: page: file:
/assign
/assign
This fixes this issue.
please avoid assigning yourself to a issue that is already assigned to somebody else.


Question: ### Configure TLS Worker nodes require three keys: `ca.pem`, `worker.pem`, and `worker-key.pem`.  We've already generated <del> `ca.pem` for use on the Master.  The worker public/private keypair should be generated for each Kubernetes node. </del> <ins> `ca.pem` and `ca-key.pem` for use on the Master.  The worker public/private keypair should be generated for each Kubernetes node. </ins> 1.  Create the file `worker-openssl.cnf` with the following contents.

Step 2 of says that it uses the generated earlier. In fact it also uses the ca- generated earlier.


Question: 下表列出所有受支持的资源类型及其缩写别名: <!-- <del> (This output can be retrieved from `kubectl api-resources`, and is accurate as of Kubernetes 1.13.3.) </del> <ins> (This output can be retrieved from `kubectl api-resources`, and is accurate as of Kubernetes 1.19.1.) </ins> --> <del> (以下输出可以通过 `kubectl api-resources` 获取，内容以 Kubernetes 1.13.3 版本为准。) </del> <ins> (以下输出可以通过 `kubectl api-resources` 获取，内容以 Kubernetes 1.19.1 版本为准。) </ins> <!-- <del> | Resource Name | Short Names | API Group | Namespaced | Resource Kind | </del> <ins> | NAME | SHORTNAMES | APIGROUP | NAMESPACED | KIND | </ins> |---|---|---|---|---| <ins> | `bindings` | | | true | Binding | </ins> | `componentstatuses` | `cs` | | false | ComponentStatus | | `configmaps` | `cm` | | true | ConfigMap | | `endpoints` | `ep` | | true | Endpoints | <ins> | `events` | `ev` | | true | Event | </ins> | `limitranges` | `limits` | | true | LimitRange | | `namespaces` | `ns` | | false | Namespace | | `nodes` | `no` | | false | Node |

This is a Bug Report Problem: The resource type list on is about v1.13.3 which is too old. We are not obliged to keep the list updated on every release, but having the list updated to a supported version is still desireable. Proposed Solution: Update the list to reflect what we have today. Page to Update:
ref:
/assign
fixed. /close
Closing this issue. <detailsIn response to : fixed. /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: "name-virtual-host-ingress-no-third-host": {&networking.Ingress{}}, "namespaced-params":                       {&networking.IngressClass{}}, "networkpolicy":                           {&networking.NetworkPolicy{}}, <ins> "networkpolicy-multiport-egress":          {&networking.NetworkPolicy{}}, </ins> "network-policy-allow-all-egress":         {&networking.NetworkPolicy{}}, "network-policy-allow-all-ingress":        {&networking.NetworkPolicy{}}, "network-policy-default-deny-egress":      {&networking.NetworkPolicy{}},

I spent one hour to do one sample exercice about network policy because of your wrong configuration !!! +++++++++++++++++++++ policyTypes: # should remove space in the 2nd & 3rd line Ingress Egress ++++++++++++++++++++++ egress: to: ipBlock: cidr: 10.0.0.0/24 ports: # "-" is missing before ports protocol: TCP port: 5978
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 Invalid manifest in Network Policies page Thanks for reporting the bug /kind bug /language en Please paste in the entire invalid manifest (surround it by <tt`</ttif you can) so we know which part of the page is wrong. We could guess, but it's easier if you're explicit about this
/triage accepted /assign


Question: <!-- Use the output from the previous commands to create a yaml file as follows. The base64 encoded value should all be on a single line. --> <del> 使用前面命令的输出来创建yaml文件，如下所示。 base64编码的值应全部放在一行上。 </del> <ins> 使用前面命令的输出来创建 yaml 文件，如下所示。 base64 编码的值应全部放在一行上。 </ins> ```yaml apiVersion: "v1"

Nginx https 404
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
Hi It sounds like you wanted to provide feedback about a web page. Which web page was that? /triage needs-information